菜单
Lists all screens in a Stitch project. Use this after generate_screen_from_text to find the screenId of the newly generated screen, then call stitch-mcp-get-screen to retrieve it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | stitch-mcp-list-screens |
| description | Lists all screens in a Stitch project. Use this after generate_screen_from_text to find the screenId of the newly generated screen, then call stitch-mcp-get-screen to retrieve it. |
| allowed-tools | ["stitch*:*"] |
Lists all screens contained within a specific Stitch project. You typically call this right after generate_screen_from_text to find the screenId of the screen that was just created.
Only use this skill when the user explicitly mentions "Stitch".
generate_screen_from_text — to find the new screen's IDscreenId to call get_screenImportant: Use the projects/ID format — not the numeric ID alone.
{
"name": "list_screens",
"arguments": {
"projectId": "projects/3780309359108792857"
}
}
✅ "projects/3780309359108792857"
❌ "3780309359108792857"
{
"screens": [
{
"name": "projects/3780309359108792857/screens/88805abc123def456",
"title": "Login Screen",
"screenshot": {
"downloadUrl": "https://storage.googleapis.com/..."
},
"deviceType": "MOBILE"
}
]
}
screenId from the name field:
"projects/3780309359108792857/screens/88805abc123def456" → screenId = "88805abc123def456"stitch-mcp-get-screen with the numeric projectId and screenIdFor the next call (get_screen), you need the numeric IDs for both project and screen:
projectId → 3780309359108792857 (strip projects/ prefix)screenId → 88805abc123def456 (strip projects/.../screens/ prefix)Conversational design ideation agent that researches trends, explores visual directions, and refines ideas through adaptive questioning — then produces a rich PRD document and auto-generates Stitch screens. Your design buddy that thinks deeply before designing.
Master entry point for all Stitch design workflows. Routes from user request → design spec → prompt assembly → screen generation → iteration (edit, variants, design systems) → design system extraction → framework conversion (Next.js, Svelte, HTML, React Native, or SwiftUI) → optional quality pass.
Analyzes a Stitch project's screens and synthesizes a natural-language DESIGN.md — visual atmosphere, color palette with hex values, typography rules, and Stitch-ready prompt snippets. Use this before stitch-loop or any multi-page build to establish design consistency.
Extracts a Stitch design and generates production code artifacts — CSS custom properties with dark mode tokens, a Tailwind v4 @theme block, and a semantic design system document. Run this before framework conversion skills.
Creates a reusable Stitch Design System from theme tokens — colors, fonts, roundness, saturation. Can be applied to future screens for visual consistency.
Creates a new Stitch project container (a design workspace). Call this when starting a new design session to get a projectId for screen generation.