From stitch
Orchestrate Stitch bridge with SCE contracts: analyze, compose, invoke, consume, and sync. Use when: 'stitch bridge', 'analyze stitch', 'sync stitch'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/stitch:stitch-bridgeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Thin skill contract:
Thin skill contract:
context_preflight.context_*.analyze: detect gaps in .stitch/ artifacts.compose-prompt: produce context-grounded prompt.invoke: run Stitch generation/editing (explicit confirmation required).consume: ingest generated assets to repository artifacts.sync: trigger downstream conversion pipeline.| Subcommand | Native MCP Tools Used |
|---|---|
analyze | mcp__stitch__get_project + mcp__stitch__list_screens + mcp__stitch__get_screen + local .stitch/ read |
compose-prompt | local logic only (no MCP) |
invoke | mcp__stitch__generate_screen_from_text, mcp__stitch__edit_screens, or mcp__stitch__generate_variants (user confirmation required) |
consume | mcp__stitch__get_screen (for htmlCode.downloadUrl + screenshot.downloadUrl) |
sync | local triggers only (DSE/GDU pipeline) |
npx claudepluginhub murillodutt/cellm --plugin stitchGuides step-by-step installation of Stitch MCP server and stitch-kit plugin for Claude Code, Codex CLI, Cursor, and VS Code. For first-time setup, connection issues, or new user onboarding.
Generates UI screens in Google Stitch from markdown prompt files using MCP tools. Parses sections by markers, sends prompts for generation, fetches images and code, saves to exports and code folders.
Implements an autonomous iterative loop for building websites using Stitch MCP tools and baton-passing via .stitch/next-prompt.md for multi-step frontend construction.