gabelul/stitch-kit

stitch-mcp-update-design-system

Updates an existing Stitch Design System's theme, tokens, or guidelines. Requires the asset name from create or list operations.

First seen Mar 21, 2026

Installation

$ npx skills add gabelul/stitch-kit --skill stitch-mcp-update-design-system

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from gabelul/stitch-kit · top by installs.

npx skills add gabelul/stitch-kit

Browse all from gabelul/stitch-kit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 43
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsstitch*:*

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,112 B
  • docs SUMMARY.md 167 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 38 installs

SKILL.md

Stitch MCP — Update Design System

Updates an existing Stitch Design System. Use this to modify theme properties, design tokens, or style guidelines without creating a new design system.

Critical prerequisite

Only use this skill when the user explicitly mentions "Stitch".

You must have the design system's asset name before calling this. If you don't have one:

  • List existing design systems via stitch-mcp-list-design-systems
  • Or use the name returned from stitch-mcp-create-design-system

When to use

  • User wants to modify colors, fonts, or roundness of an existing design system
  • After reviewing a design system and wanting to adjust specific properties
  • Updating design tokens after a brand refresh

Call the MCP tool

{
  "name": "update_design_system",
  "arguments": {
    "name": "assets/15996705518239280238",
    "projectId": "3780309359108792857",
    "designSystem": {
      "displayName": "SaaS Dashboard Theme v2",
      "theme": {
        "colorMode": "DARK",
        "headlineFont": "GEIST",
        "bodyFont": "GEIST",
        "labelFont": "GEIST",
        "roundness": "ROUND_TWELVE",
        "customColor": "#818CF8"
      }
    }
  }
}

Parameter reference

Three sibling top-level arguments — name is not nested inside designSystem:

Argument Type Required Description
name string Yes Asset identifier with the assets/ prefix, e.g. assets/15996705518239280238. Top-level, not inside designSystem.
projectId string Yes Bare numeric project id, no projects/ prefix
designSystem object Yes {displayName, theme} — see below

designSystem{displayName, theme} only

Field Type Required Description
displayName string Yes Human-readable name
theme DesignTheme Yes Visual configuration (see stitch-mcp-create-design-system for the full field reference)

updatedesignsystem takes the asset id prefixed (assets/159967...), while applydesignsystem takes the same id bare. Two tools, same identifier, different formats.

designTokens and styleGuidelines are not accepted — the live API has no such fields on DesignSystem. Don't send them.

Note: This is a full replacement, not a merge. Include all theme fields you want to keep, not just the ones you're changing.

Output

Returns the updated Asset object:

{
  "name": "assets/15996705518239280238",
  "displayName": "SaaS Dashboard Theme v2",
  "designSystem": { ... }
}

After updating

  • Offer: "Re-apply this updated design system to existing screens?" → stitch-mcp-apply-design-system
  • Screens generated before the update won't automatically reflect changes — they need to be re-applied