Install
$ agentstack add skill-gabelul-stitch-kit-stitch-mcp-apply-design-system ✓ 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 — Apply Design System
Applies a previously created Stitch Design System to one or more screens. This updates the screen's visual theme (colors, font, roundness) to match the design system, ensuring visual consistency across a project.
Critical prerequisite
Only use this skill when the user explicitly mentions "Stitch".
You must have:
- A
projectId(numeric) - One or more
screenIdvalues (numeric) - An
assetIdfrom a design system (fromlist_design_systemsorcreate_design_system)
When to use
- After creating a design system and wanting to apply it to screens
- User says "make all screens match this theme" or "apply the design system"
- The orchestrator's Step 5b stores an assetId and offers to apply it
- Ensuring visual consistency across a multi-screen project
Call the MCP tool
{
"name": "apply_design_system",
"arguments": {
"projectId": "3780309359108792857",
"selectedScreenIds": ["88805abc123def456", "99906xyz789ghi012"],
"assetId": "ds_abc123"
}
}
Parameter reference
projectId — numeric ID only, no prefix
✅ "3780309359108792857"
❌ "projects/3780309359108792857"
selectedScreenIds — array of numeric screen IDs
✅ ["88805abc123def456"]
❌ ["projects/123/screens/88805abc123def456"]
All selected screens will have the design system applied.
assetId — the design system identifier
The name field from a design system asset, or just the ID portion:
✅ "ds_abc123"
Get this from:
stitch-mcp-list-design-systems→ extract from thenamefield of each assetstitch-mcp-create-design-system→ returned in the responsenamefield
Output
Returns updated screen data reflecting the applied design system.
After applying
- Re-fetch affected screens:
stitch-mcp-get-screenfor each screenId - Show updated screenshots to the user
- Offer:
- "Edit the updated screens?" →
stitch-mcp-edit-screens - "Convert to code?" → framework conversion
- "Apply to more screens?" → another
apply_design_systemcall
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.