What the user does and what they get in the end.
- acceptance criterion: what must be true when it is done
- one more: an edge case or a limit
You talk to your agent — the agent writes into Studio, Studio checks, computes and shows every change live. Five chapters on Studio's real components.
Start with an idea: tell your agent what you want to build.
The agent is connected to Coddle over MCP and sees your projects.
Message your agent…
One or two sentences: what it is, who it is for and what problem it solves.
looks around without an account
signs up and uses the main feature
manages content and users
What the user does and what they get in the end.
usersemail, name, when they signed up
which service sends the letters, and which letters
Steps in the order of the work: environment, database, sign-in, a step per feature, screens, integrations, release. The agent ticks them as it builds (spec_tick), and the progress shows here.
The canvas, the checks, the sandbox, the simulation and the plan here are Studio's own components. The query and the migration results come from real Postgres, the load from Studio's engine.