StitchFlow
Orchestrates Google Stitch (MCP or CLI toolkit) to generate/edit/export UI screens — needs a Stitch API key.
Werkt met setup
Wat het doet
Routes design requests (new screen, edit, variants, multi-screen prototype, DESIGN.md/design-system work, local HTML+screenshot export) to the right Google Stitch workflow, preferring native Stitch MCP tools and falling back to a bundled Node CLI toolkit. Triggers on explicit Stitch/StitchFlow requests or prototype/variant/export asks, but every real action calls the external, API-key-gated Google Stitch service.
Testrapport
Every workflow bottoms out in `npm run generate` etc. against the bundled stitch-starter CLI, which lives outside the skill folder at $HOME/.agents/stitch-starter and requires a Google Stitch API key; ran it for real with no key and it failed cleanly ('STITCH_API_KEY is not set... copy .env.example to .env') rather than producing anything, so a plain SKILL.md copy is non-functional until install.sh + an API key are added.
Getest op: 2026-07-15 · Claude Code 2.x (agent harness)
Installatie
git clone https://github.com/yshishenya/stitchflow.git
mkdir -p ~/.claude/skills
cp -r stitchflow/skills/stitchflow ~/.claude/skills/stitchflow
# NOT sufficient alone: the skill body executes commands against ${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}, a toolkit outside the skill folder — also run `bash stitchflow/install.sh --target claude` and set STITCH_API_KEY in the toolkit .env Commando's en voorbeeldprompts
/stitchflowOrchestrates Google Stitch (MCP or CLI toolkit) to generate/edit/export UI screens — needs a Stitch API key.
Skills reageren op gewone verzoeken — geen commando's om te onthouden. Na installatie activeren prompts zoals deze de skill (in het Engels):
generate a pricing page screen design using Google Stitchcreate a few variants of this onboarding screen through Stitchexport this multi-screen prototype as local HTML with screenshots