Install
$ agentstack add skill-gabelul-stitch-kit-stitch-mcp-list-design-systems ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gabelul
- Source: gabelul/stitch-kit
- License: Apache-2.0
- Homepage: https://booplex.com/projects/stitch-kit-design-intelligence-for-ai-agents
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.