# For designers

A designer's path through EasyCode: the studio, the design system record, design requests, reviews on live frames and the board.

## What does EasyCode do for a designer?

You design where the code is. In the **Studio**, a session on your own harness drafts a prototype from a prompt or
from a task's acceptance criteria, in your design system's tokens. You share it, collect comments and hand it to the
developers. When your team keeps a design system, EasyCode reads it from the code, gives it to every session, and lets
you review each design change on live frames before it merges.

> **In the pilot**
>
> The design system module, with the **Design systems** rail item and every page under Design system, is in the pilot.
> It is on for pilot orgs first. An org admin can tell you whether your org has it. The **Studio** works without it.

## Your path

Follow these pages in order. Each line says why it matters to you.

### Get set up

1. [Quickstart](/setup/quickstart): join your org and find **Studio** in the rail.
2. [Desktop app](/setup/desktop-app): studio sessions start there, and films render there. Reading, sharing and
   commenting work on the web.

### Make and share in the studio

3. [Share and review in the studio](/guides/studio-share-and-review): start a prototype, a deck or a drawing,
   publish versions, and use **Make a view-only link** for people outside the org.
4. [From design to build](/scenarios/design-to-build): how an approved design becomes the task, the session and the
   pull request that builds it.

### Keep the design system

5. [The design system record](/design-system/the-record): a system's sources, releases, tokens and components, read
   from the code at every merge and tag.
6. [Design in every session](/design-system/in-every-session): a product declares the system it uses, so every
   session builds with that release's parts and stops when one is missing.
7. [Design requests](/design-system/design-requests): a missing part becomes a request that blocks the task needing
   it until a release ships the part.
8. [Review a design change on live frames](/design-system/review-on-live-frames): the default branch beside the pull
   request, by theme and device, with comments pinned to the tile and your verdict.
9. [The audit and the adoption number](/design-system/audit-and-adoption): what each product really uses, and how
   much of it comes from your system.
10. [The design board](/design-system/design-board): a shared canvas of live frames, components, stickies and task
    cards, with everyone's cursors.

## What can I make in the studio?

**Studio** offers these starts. Each opens a session on your own harness, in the desktop app:

- **Prototype from a description**: screens and a journey from a prompt or the acceptance criteria.
- **Prototype from the running app**: a page from the built-in browser, captured as a frame.
- **Walkthrough of a pull request**: the change in reading order, with proof.
- **Deck**: slides at 1920 × 1080, with present mode and PDF.
- **Film**: from a beat sheet or a pull request, with voice, music and sound effects.
- **Drawing**: an illustration or a diagram.

The agent publishes a version with [`studio_publish`](/reference/mcp-tools#studio-publish) and answers your comment threads with [`studio_reply`](/reference/mcp-tools#studio-reply). A developer's session reads the approved design with [`studio_handoff`](/reference/mcp-tools#studio-handoff).

## Where next

- [X-ray and conformance](/design-system/x-ray-and-conformance): label a live page's elements by system, in the
  desktop browser.
- [Docs from the record](/design-system/docs-from-the-record): component and token docs from a release.
- [Kill switches and modules](/reference/kill-switches-and-modules): what the [`studio`](/reference/kill-switches-and-modules#studio), [`design`](/reference/kill-switches-and-modules#design) and [`board`](/reference/kill-switches-and-modules#board) switches turn off.
