StudioOSFive agents, one file

The five AI agents behind every site, and their rules

A strategist, a copywriter, a designer, a developer and a critic build each site. All five work from one file, blueprint/blueprint.json.

An orchestrator dispatches them one at a time, checks what comes back and keeps blueprint/status.md current. It writes no strategy, copy, design or code itself. Think of it as a project manager with no opinion on fonts.

Each profile below says which stages the agent works in, what it reads, what it writes, and what it is never allowed to do.

run.png — seed 0x28b7

What each agent reads, writes and never does

  1. studio-strategist.md

    Strategist

    Works in
    Strategy, and the fixes after the text review.
    Reads
    The intake and every file under Material, the notes on each reference (never the images), and the strategy part of the rubric.
    Writes
    The goal, audience and tone, the sitemap, each section's notes, the requirements and the acceptance criteria, all in blueprint/blueprint.json.
    Never
    Writes copy, picks fonts, colours, layout or motion, or invents a fact about the business.
  2. studio-copywriter.md

    Copywriter

    Works in
    Copy, the fixes after the text review, and the copy changes after the gate.
    Reads
    blueprint/blueprint.json, the intake and its material, the copy part of the rubric and the owner's notes.
    Writes
    The heading, body and button of every section. A missing fact becomes [NEEDS: …].
    Never
    Touches a section the owner marked final, changes the structure, or makes up a price, name or number.
  3. studio-designer.md

    Designer

    Works in
    Design directions, concept builds and the fixes after the concept review.
    Reads
    The copy in blueprint/blueprint.json, the references and their screenshots, and what Astrokit already has. With no primary reference, it picks from the owner's reference library.
    Writes
    Two notes, blueprint/concepts/a.md and b.md, one close to the references and one that pushes further, then each as a live page with the real copy in its own git worktree.
    Never
    Edits blueprint/blueprint.json, shortens copy without listing the change, adds a dependency, or builds two concepts alike to play safe.
  4. studio-developer.md

    Developer

    Works in
    Build, and the fixes after verification.
    Reads
    The chosen concept's note and code, blueprint/blueprint.json, DESIGN.md and the owner's notes.
    Writes
    The rest of the Astrokit site page by page, the footer, the design tokens in blueprint/blueprint.json and DESIGN.md, then the content in Sanity.
    Never
    Re-decides type, colour or density, rewrites copy, or pushes, deploys or adds a git remote.
  5. studio-critic.md

    Critic

    Works in
    Text review, concept review and verification.
    Reads
    The rubric, blueprint/blueprint.json, the intake, and the live pages at 1440, 768 and 390 pixels wide.
    Writes
    One round file per review under blueprint/review/, and blueprint/verification.md.
    Never
    Sees the author's reasoning, fixes the work itself, or judges from one full-page screenshot.

They pass files, not messages

HANDOFFS.md — 5 passes
  1. 01Intake to strategistblueprint/intake.md and the references, as the owner left them.
  2. 02Strategist to copywriterblueprint/blueprint.json with pages, sections and notes, and not a word of copy yet.
  3. 03Copywriter to designerThe same file with every heading, paragraph and button filled in.
  4. 04Designer to developerThe concept the owner chose at the gate: its note, its tokens, its navbar and its sections, merged into the base branch.
  5. 05Every stage to criticPaths only. Never the author's report or reasoning.

No agent talks to another. Each starts from the files and leaves its work in them, and blueprint/status.md records where the run stands, so nothing depends on what an agent remembers.

After the run, your corrections become their instructions

RETRO.md

No agent carries memory from one run to the next. Each starts from its own instructions and the files in front of it, so a correction you made on one site would be needed again on the next.

The retro closes that gap. It is a step after the run, not a sixth agent: it turns your corrections into proposed changes to the instructions the five agents read. Nothing changes without your yes, so the next run starts from instructions you have approved.

Now watch all five work through one run

The walkthrough follows a single run from the owner's side, from the intake to the retro, and shows where each agent picks up the file.

Read the walkthrough