StitchFlow

Orchestrates Google Stitch (MCP or CLI toolkit) to generate/edit/export UI screens — needs a Stitch API key.

Works with setup

Test report

Verdict
Works with setup
Score
7.6/10
Tested
Jul 15, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · 54a92b0

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.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 4/5
  • Triggers reliably 5/5
  • Output vs. baseline 5/10
  • Docs & honesty 5/5

What StitchFlow does

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.

How to install StitchFlow

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

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger StitchFlow

  • /stitchflow Orchestrates Google Stitch (MCP or CLI toolkit) to generate/edit/export UI screens — needs a Stitch API key.

It also activates on plain-language prompts like these:

  • generate a pricing page screen design using Google Stitch
  • create a few variants of this onboarding screen through Stitch
  • export this multi-screen prototype as local HTML with screenshots

Frequently asked questions

Is the StitchFlow skill free?
Yes. The skill itself is free from yshishenya/stitchflow. SkillProof publishes the install command and an independent test verdict at no cost.
Does StitchFlow work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 15, 2026. Verdict: Works with setup. 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.
What is the StitchFlow SkillProof Score?
7.6/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 5/5.
How do I install StitchFlow?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use StitchFlow with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.