stitch::manage-design-system ยท git:20260510.5532ce0 ยท 2026-05-10 ยท sha256 ef32665284c704e6

stitch::manage-design-system git:20260510.5532ce0A

Immutable. This exact content never changes and is served at /api/v1/blob/ef32665284c704e6.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_427jotdhviynufem/ef32665284c704e693bbbf0ef81b55f2f9c9b87120b488152575ee597e1468d8.json

Then /plugin install stitch-manage-design-system@markdownregistry-427jotdhviynufem in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: stitch::manage-design-system
description: >-
  Manage design systems in Stitch using MCP tools. Includes retrieval of assets,
  creating/updating design systems in Stitch, and applying them to screens.
---

# Design-System

Create a "source of truth" for your project's design language to ensure
consistency across all future screens.

> [!NOTE]
> Refer to your system prompt for instruction on handling MCP tool prefixes for
> all tools mentioned in this skill (e.g., `get_screen`, `upload_design_md`,
> `create_design_system_from_design_md`, `apply_design_system`).

## ๐Ÿ“ฅ Retrieval

To analyze a Stitch project, you must retrieve metadata and assets using the
Stitch MCP tools:

1. **Project lookup**: Use `list_projects` to find the target `projectId`.
2. **Screen lookup**: Use `list_screens` for that `projectId` to find
   representative screens (e.g., "Home", "Main Dashboard").
3. **Metadata fetch**: Call `get_screen` for the target screen to get
   `screenshot.downloadUrl` and `htmlCode.downloadUrl`.
4. **Asset download**: Use `read_url_content` to fetch the HTML code.

## ๐Ÿง  Synthesis from Description

If you need to extract a design system from existing screens, use the `design-md` skill.

If there are no existing screens (new project), or the user provides a direct description (e.g., "dark theme, blue and purple, rounded, Inter font"):

1. Map the user's vague terms to precise values using the design mappings (see `design-md` skill or `generate-design` skill).
2. Select concrete hex codes, font families, and roundness values.
3. Generate the `DESIGN.md` file (refer to `design-md` for structure).
4. Proceed to the "Create or Update Design System in Stitch" step below.

## ๐Ÿ“ Output Structure

The `DESIGN.md` file should follow the structure defined in the `design-md` skill.

## ๐Ÿš€ Create or Update Design System in Stitch

After generating `.stitch/DESIGN.md`, make sure to also create or update the
design system in Stitch using MCP tools.

**Two-step design system creation:**

> [!WARNING]
> **Checkpoint โ€” User Confirmation Required.**
> Before calling `upload_design_md`, you **MUST** pause and ask the user for
> confirmation. Present a summary of the design system you are about to create
> (display name, key colors, fonts, and roundness) and wait for explicit approval
> before proceeding. Do **NOT** call `upload_design_md` until the user
> confirms.

Read the tool schema for the exact call formats before making these calls.

1. Call `upload_design_md` with the base64 encoded content of the `DESIGN.md` file and the `projectId`. This uploads the markdown and returns the source screen ID.
2. Immediately call `create_design_system_from_design_md` with the `projectId` and `selectedScreenInstance` (constructed using the returned source screen ID and fetching the screen instance ID from `get_project`).

Once both `upload_design_md` and `create_design_system_from_design_md` have been called,
Stitch holds the design tokens at the project level โ€” you do NOT need to repeat
them in generation prompts.

## ๐ŸŽจ Apply Design System to Screens

Use `apply_design_system` to apply a design system to existing screens.

> [!IMPORTANT]
> `selectedScreenInstances` must contain **only** `id` and `sourceScreen` โ€” do
> NOT include position/dimension fields (`x`, `y`, `width`, `height`) or the
> request will fail with "invalid argument". Get the screen instance IDs from
> `get_project`.

```json
{
  "projectId": "...",
  "assetId": "...",
  "selectedScreenInstances": [
    {
      "id": "...",
      "sourceScreen": "projects/.../screens/..."
    }
  ]
}
```

**How to get the required IDs:**
1. Call `get_project` to retrieve `screenInstances` โ€” each has an `id` and
   `sourceScreen`.
2. Call `list_design_systems` to retrieve the design system `name` (format:
   `assets/{assetId}`) โ€” use the part after `assets/` as the `assetId`.
3. Filter out any instances with `type: "DESIGN_SYSTEM_INSTANCE"` โ€” only pass
   real screens.

## ๐Ÿ“‹ Update Project Metadata

After writing `.stitch/DESIGN.md`, also create or update `.stitch/metadata.json`
to track the `projectId`, `title`, all known screens, and design system summary.
See [examples/metadata.json](examples/metadata.json) for the format.

## Schema Reference

See [reference/tool-schema.md](reference/tool-schema.md) for the full
`designSystem` object schema with all available options.

## ๐Ÿ’ก Best Practices

Refer to the `design-md` skill for best practices on describing design elements.