UX Stitch Generate Skill
WorkflowSkills Project Context
Before acting, resolve project documentation roots:
- Look for a
[DOC]-*directory at project root. - If found, set
DOC_ROOTto that directory andUX_DOCS_ROOTto[DOC]-*/11-UX-DesignOps. - If
[DOC]-*is absent, stop and ask to initialize project documentation first; never write persistent UX documentation todocs/obsidian. - If UX docs do not exist inside
[DOC]-*, run or followux-bootstrap. - Read
DESIGN.mdand related screen, component, or flow docs.
Goal
Create Stitch exploration inputs that produce usable, professional UI variants without AI slop.
Stitch MCP Usage
Use Stitch MCP tools when available:
list_projectsandget_projectbefore creating new project context.create_projectonly when the user asks for a new Stitch project or no suitable project exists.list_design_systemsbefore selecting a design system.upload_design_mdandcreate_design_system_from_design_mdwhen syncingDESIGN.md.apply_design_systemwhen a target screen and design system are known.
Current MCP limitations must be stated when relevant: direct screen generation, HTML upload, HTML extraction, React/shadcn conversion, and stitch-loop may require the official google-labs-code/stitch-skills ecosystem if not exposed in the active MCP.
Output
UX_DOCS_ROOT/07-Stitch/Prompts/[target].mdUX_DOCS_ROOT/07-Stitch/Project_Map.md- Optional operational prompt in
design/stitch/prompts/[target].md
Rules
- Do not implement code in this skill.
- Do not invent product rules or fake data.
- Include at least two variants when exploring.
- Include strict constraints against generic gradients, decorative cards, fake metrics, and unsupported visual effects.