stitch-mcp-list-design-systems | stitch-kit | ClaudePluginHub

Skill

stitch-mcp-list-design-systems

From stitch-kit

Lists available Stitch Design Systems across projects or filtered by projectId, returning asset names for apply and update operations. Use before applying themes, updating, or checking existing ones.

$

npx claudepluginhub gabelul/stitch-kit --plugin stitch-kit

Tool Access

This skill is limited to using the following tools:

stitch*:*

Preview

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

SKILL.md

Similar Skills

stitch-mcp-get-project

22

Retrieves metadata for Stitch projects including title, design theme, timestamps, and screen list. Use to inspect before generating consistent UI screens; requires explicit Stitch mention.

1 tool

stitch-design-md

328

Analyzes Stitch projects via MCP tools to synthesize semantic design systems into DESIGN.md, extracting style guides and design tokens for colors, typography, spacing from screens.

3 files4 tools

partme-ai-full-stack-skills

wds-7-design-system

35

Create, import, browse, and maintain design system components and tokens. Useful for developers managing UI design assets across projects.

20 files

Stats

Stars22

Forks3

Last CommitFeb 25, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

theme-management

Help us improve

Share bugs, ideas, or general feedback.

Stitch MCP — List Design Systems

Lists all available Stitch Design Systems. These are reusable theme configurations (colors, fonts, roundness, saturation) 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/ds_abc123",
      "displayName": "SaaS Dashboard Theme",
      "designSystem": {
        "theme": {
          "colorMode": "LIGHT",
          "font": "DM_SANS",
          "roundness": "ROUND_EIGHT",
          "saturation": 3,
          "customColor": "#6366F1",
          "backgroundLight": "#FFFFFF",
          "backgroundDark": "#18181B"
        },
        "designTokens": "...",
        "styleGuidelines": "..."
      }
    }
  ]
}

After listing

Present as a readable table:

#	Name	Font	Color	Mode	Asset ID
1	SaaS Dashboard Theme	DM Sans	#6366F1	Light	`ds_abc123`

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 — this is the assetId needed for apply_design_system.