Demo · 3 minutes

Studio and your agent: from an idea to a built project

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.

Chapter 1 of 5 · Spec

Start with an idea: tell your agent what you want to build.

Your agentcoddle · MCP

The agent is connected to Coddle over MCP and sees your projects.

Message your agent…

coddle.uz/studio/you/barbershop/spec
Studio/barbershop/SpecSpec
savedlive

One or two sentences: what it is, who it is for and what problem it solves.

0 of 3 acceptance criteria done0%
Data schemathe project has no DB schema
Architecturethe project has no architecture
3
  • looks around without an account

  • signs up and uses the main feature

  • manages content and users

2criteria 0/3
0/2

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
0/1
  • email and password; a forgotten password can be reset
3
  • home: what the product is and how to start
  • the main feature (user)
  • content and users (admin)
1
  • users

    email, name, when they signed up

1
  • which service sends the letters, and which letters

1
  • what is deliberately not in the first version
1
  • what is still to be decided
Build plan

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.

0:00 / 2:00

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.