stitchflowlisted

# StitchFlow Use this skill when the user wants to create a new screen, refine an existing one, generate design variants, or export local HTML and screenshots through Stitch. It uses the local toolkit at `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}` instead of a Stitch MCP tool. ## Local setup - Toolkit root: `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}` - API key is expected in `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/.env` - Outputs are saved to `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/runs` - The latest single-screen result is tracked in `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/runs/latest-screen.json` ## When to use - The user says to use Stitch or StitchFlow - The user wants a screen generated from a brief, spec, or rough idea - The user wants design variants before implementation - The user wants targeted visual edits to a generated screen - The user wants HTML and screenshots exported locally for review ## Workflow routing - New screen from a prompt or brief: Read [text-to-design](workflows/text-to-design.md) - Targeted changes to an existing Stitch screen: Read [edit-design](workflows/edit-design.md) - Multiple directions from one base screen: Read [variants](workflows/variants.md) ## Core rules 1. Before any Stitch command, rewrite the user request into a stronger design prompt. 2. If the user already has a codebase or UI context, inspect it first and carry that context into the prompt. 3. Prefe