The Studio
Designs and diagrams, live.
Ask for a design, an architecture or the sequence flows — the agent writes a self-contained proposal, and Team previews it live beside the terminal. You iterate in plain language; every save hot-reloads. Approve, and it becomes a flagged, linked artifact in Docs.
- /twd-design — polished UI mockups, previewed at mobile (in a phone frame) and desktop widths
- /twd-architecture — C4-style context/containers/components with labeled edges and a Decisions note
- /twd-seq-diagram — one sequence diagram per scenario: happy path, failures, alt/opt fragments
- Approve publishes to Docs as [Design] / [Architecture] / [Sequence], linked to the task
- Approved artifacts are must-follow context: future FE and backend work is briefed with them automatically
- Design under review? Author, reviewer and the live preview share one three-pane split
> /twd-design DB-0102
📋 Brief posted to the board
🎨 Visual proposal ready — Open preview ⌘⏎
[ AUTHOR ] [ STUDIO · Mobile | Desktop ]
"make the header darker" → saved → reloaded
Approve ✓ → Docs: [Design] DB-0102 — main screen
Architecture you can see
From prompt to artifact, not from prompt to prose.
Designs, container diagrams and sequence flows are concrete files you watch evolve — not paragraphs you have to imagine. Once approved, they stop being suggestions: they are the contract the next tasks are briefed with.
