agentsclimarketplace

Stitch mcp list design systems

Skill gabelul/stitch-kit/skills/stitch-mcp-list-design-systems

Lists all Stitch Design Systems, optionally filtered by project. Returns asset names needed for apply and update operations.From its SKILL.md

Install
npx -y skills add gabelul/stitch-kit --skill stitch-mcp-list-design-systems

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 1 command, including `list_design_systems`.

SKILL.md

2.3 KB, 549 tokens by cl100k_base, as published. Nobody here has run it

Stitch MCP — List Design Systems

Lists all available Stitch Design Systems. These are reusable theme configurations (colors, fonts, roundness) that can be applied to screens for visual consistency across a project.

Critical prerequisite

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

When to use

  • Before applying a design system — need to find the assetId
  • User asks "what design systems do I have?"
  • The orchestrator checks for existing design systems during project setup (Step 4b)
  • Before creating a new design system — check if one already exists

Call the MCP tool

{
  "name": "list_design_systems",
  "arguments": {
    "projectId": "3780309359108792857"
  }
}

projectId — numeric ID only, optional

✅ "3780309359108792857"
❌ "projects/3780309359108792857"

If omitted, returns all design systems across all projects.

Output schema

Returns an array of Asset objects:

{
  "assets": [
    {
      "name": "assets/15996705518239280238",
      "displayName": "SaaS Dashboard Theme",
      "designSystem": {
        "theme": {
          "colorMode": "LIGHT",
          "font": "DM_SANS",
          "roundness": "ROUND_EIGHT",
          "customColor": "#6366F1",
          "backgroundLight": "#FFFFFF",
          "backgroundDark": "#18181B"
        }
      }
    }
  ]
}

After listing

Present as a readable table:

#NameFontColorModeAsset ID
1SaaS Dashboard ThemeDM Sans#6366F1Light15996705518239280238

Then offer:

  • "Apply one of these to a screen?" → stitch-mcp-apply-design-system
  • "Update an existing design system?" → stitch-mcp-update-design-system
  • "Create a new design system?" → stitch-mcp-create-design-system

Extract the name field from each asset (assets/15996...). It's used two different ways depending on the next call:

  • apply_design_system's assetId — strip the assets/ prefix, pass the bare numeric id
  • update_design_system's designSystem.name — pass name as returned, with the prefix

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in 549 tokens

Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06

  • Commit to a bold aesthetic directionin 31 of 1179, across 24 files
  • Prefer component composition over inheritancein 28 of 1179, across 14 files
  • Animate only transform and opacity propertiesin 27 of 1179, across 22 files
  • Memoize expensive computations with useMemoin 26 of 1179, across 13 files
  • Use semantic HTML elementsin 24 of 1179, across 23 files
  • Virtualize long lists for performancein 21 of 1179, across 10 files
  • Use CSS variables for design tokensin 20 of 1179, across 14 files
  • Implement loading, empty, and error statesin 20 of 1179
  • Lazy load heavy components with Suspensein 19 of 1179, across 8 files
  • Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
  • Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
  • Use compound components for related UI elementsin 18 of 1179, across 7 files

Said here and by no other author read

  • Use only when user mentions Stitch
  • Call list_design_systems tool
  • Present results as a readable table
  • Offer to apply update or create design systems
  • Strip assets prefix for apply_design_system assetId
  • Use full name with prefix for update_design_system

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.