Stitch Manage Design System

This skill is a catalog-normalized import from https://github.com/google-labs-code/stitch-skills at commit 3f64079d75d025bc5890c73669f27c26a2d80b31, source path plugins/stitch-design/skills/manage-design-system. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them.

When to Use This Skill

• Use when .stitch/DESIGN.md should become a Stitch design system or an existing design system should be listed or applied.
• The task involves Google Stitch project IDs, .stitch/ artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation.
• The broader stitch-design router points here as the narrowest workflow.

Workflow

1. Create or identify the target project; use create_project only when a new project is appropriate.
2. Inspect .stitch/DESIGN.md for project name, colors, type, shape, component, layout, and anti-pattern rules.
3. For small DESIGN.md files, base64-encode UTF-8 content and call upload_design_md with the numeric project ID; for the bundled helper, pass --generated-by with the calling skill or agent name.
4. Immediately call create_design_system_from_design_md with the returned screen instance id and sourceScreen.
5. Use list_design_systems to confirm the design-system asset exists for the project.
6. Use apply_design_system only with valid selected screen instance id and sourceScreen values.

Local Assets