UX Stitch Iterate 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. - Read
DESIGN.md,UX_DOCS_ROOT/07-Stitch/Project_Map.md, and related UX docs.
Goal
Improve an existing Stitch direction while preserving product context and documented decisions.
Stitch MCP Usage
Use get_project and list_screens when project ID is known. Use list_design_systems and apply_design_system when a design system must be checked or applied.
Output
Update:
UX_DOCS_ROOT/07-Stitch/Project_Map.mdUX_DOCS_ROOT/10-Decisions/Decision_Log.mdUX_DOCS_ROOT/07-Stitch/Prompts/[target]-iteration.md
Rules
- Do not treat Stitch output as source of truth.
- Preserve
DESIGN.mdand WorkflowSkills docs as constraints. - Record selected variant, rejected directions, and rationale.
- If MCP cannot perform the requested operation, document the manual Stitch step or delegate to official Stitch Skills.