Your vibe-coded MVP works. Now make it something an AI agent can keep building.

A developer built UECA-React, a React framework designed for AI coding agents in which every component follows an identical shape — a struct (props, events, methods, children, lifecycle), a model hook, and a functional component — so an agent that has seen one component has seen the pattern. The framework, installed via npm install ueca-react and npx ueca-react-skills, is intended to let vibe-coded prototypes be rewritten into structured projects with components composed into screens, a barebone app structure, and a message bus that abstracts the API. A UECA.TraceViewerButton component added to the app root opens a live view of the component tree, message bus, and bindings so the architecture can be inspected without reading the code.

You asked an AI for an app and got a working prototype: one HTML file, some dashboard, maybe a 3D model you can spin around. It's impressive. Then you ask for the next feature, and the agent breaks two old ones. This is the usual end of a vibe-coded MVP. Everything lives in one pile, with no real architecture. As the code grows, the agent's context fills up, it gets confused, and every change becomes a gamble. A human can't easily make sense of it either. I built UECA-React , a React framework designed for AI agents. Every component has exactly the same shape: a struct props, events, methods, children, lifecycle , a model hook, and a functional component. At every level of the app, top or bottom, the structure is identical. That uniformity is what helps the agent. It doesn't need your whole codebase in its head, because once it has seen one component, it has seen the pattern. npm install ueca-react npx ueca-react-skills Rewrite this app using UECA-React. In my experience the rewrite looks nearly identical on screen, but underneath you now have a real project: components composed into screens, a barebone app structure to build on, and a message bus that abstracts the API, so the agent works only with components and their interactions. From that point, adding features is incremental. No rabbit holes, no collateral damage. Add <UECA.TraceViewerButton / to your app root to open a live view of the component tree, the message bus, and every binding. Even if an agent wrote all the code, you can check the architecture without reading it. I'll share the origin story in the next post: how a legacy-app rescue and an old Delphi habit led to this framework. Have a vibe-coded prototype stuck at "works, but can't grow"? Tell me in the comments what it is.