By role

For designers

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

Last updated November 15, 2026View as Markdown

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: join your org and find Studio in the rail.
  2. Desktop app: studio sessions start there, and films render there. Reading, sharing and commenting work on the web.

Make and share in the studio

  1. Share and review in the studio: start a prototype, a deck or a drawing, publish versions, and use Make a view-only link for people outside the org.
  2. From design to build: how an approved design becomes the task, the session and the pull request that builds it.

Keep the design system

  1. The design system record: a system's sources, releases, tokens and components, read from the code at every merge and tag.
  2. Design 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.
  3. Design requests: a missing part becomes a request that blocks the task needing it until a release ships the part.
  4. Review a design change on live frames: the default branch beside the pull request, by theme and device, with comments pinned to the tile and your verdict.
  5. The audit and the adoption number: what each product really uses, and how much of it comes from your system.
  6. The 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 and answers your comment threads with studio_reply. A developer's session reads the approved design with studio_handoff.

Where next

Something wrong or missing? Suggest a change

On this page