About Project Studio
Project Studio brings diagrams, requirements, schedules, and notes into one document. Start with a question or an idea, then add views as you work out what to build and how to explain it.
What you can use it for
Website planning
Map the pages visitors need, trace a journey such as registering for a workshop, and describe what each page should show when a form is incomplete or registration is closed.
Application design
Define requirements and acceptance criteria, map screens and their states, and show how users, services, and data stores interact with a C4 architecture diagram.
Business workflows
Show how an appointment, order, or approval moves from one state to another. Capture who does what, where handoffs happen, and which exceptions people need to handle.
Data and domain modeling
Use an entity-relationship diagram to design records and their connections. Build a common vocabulary (ontology) to agree on what terms like customer, order, and reservation mean and how they relate.
Discovery and scheduling
Organize questions and ideas with a mind map, then use a Gantt chart to see which tasks can overlap and which depend on earlier work.
Design review and handoff
Link requirements to the diagrams and views that explain them. Put the relevant views and notes in a PDF that a reviewer can read and a collaborator can reopen in Project Studio.
Hand off an app design to a coding agent
Choose File → Export → Advanced → Markdown handoff to put your architecture, linked SVG diagrams, requirements, and architecture decision records (ADRs) into a project repository. An agent can start at docs/architecture.md, follow a link to a diagram or acceptance criteria, and read why a design decision was made.
An architecture decision record explains what the team decided, why it chose that option, and what trade-offs follow.
my-app/
└── docs/
├── architecture.md
├── requirements.md
├── diagrams/
│ └── diagram-id-registration-journey.svg
└── adr/
├── README.md
└── 0001.md
A whole-project handoff includes every ADR automatically. For a feature addition, use a named Document View with just the relevant diagrams and requirements. Add an Architecture decisions block to that view to include the decisions the developer needs.
The workshop registration example includes an ADR about what happens when two people try to book the last place.
Try a website plan
The workshop registration example shows how a visitor finds a workshop and signs up. Open it to explore the page flow, page states, and requirements. The browser demo runs locally and needs no account.