| name | stitch-react-components |
| version | 2.0 |
| last_updated | 2026-08-29T00:00:00.000Z |
| tags | ["stitch","react","typescript","components","frontend"] |
| description | Convert Stitch HTML and screenshots into modular Vite/React/TypeScript components, or sync existing components to updated Stitch designs, with local architecture and validation checks. |
| license | Apache-2.0 |
Stitch React Components
This skill is a catalog-normalized import from https://github.com/google-labs-code/stitch-skills at commit 7b53207b94e62911777d53d4238b5f8c88c2b519, source path plugins/stitch-build/skills/react-components. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them.
When to Use This Skill
- Use when a Stitch screen or export should become modular React components or an existing React surface must be synchronized with newer Stitch evidence.
- The task involves Google Stitch project IDs,
.stitch/ artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation.
- The broader
stitch-design router points here as the narrowest workflow.
Workflow
- Acquire source HTML and screenshots from
.stitch/designs/, Stitch web exports, or current host-listed screen tools.
- Do not assume
get_screen or list_screens exists in this workspace.
- Record available project and screen identifiers plus the sync timestamp in
.stitch/metadata.json when that evidence exists.
- Extract current color, typography, spacing, and radius tokens from the exported HTML before editing components.
- Move static copy, image URLs, and lists into
src/data/mockData.ts.
- Create small components with
Readonly prop interfaces and isolate interactions in hooks.
- Map Stitch theme values into Tailwind/theme tokens, replace placeholder links with real application routes, and cover dark-mode states instead of scattering raw hex values.
- Run the bundled validator where dependencies are available, then run the app build or dev check.
Local Assets
examples/, resources/, references/, or reference/ are upstream support material when present. Treat SKILL.md as the source of truth if a support file mentions an unavailable MCP tool.scripts/ are optional helpers. On Windows, prefer PowerShell or Node equivalents unless Git Bash or WSL is actually available.- Keep generated
.stitch/ files out of commits unless the user explicitly wants them as durable examples.
Corrected Stitch MCP Surface
Verified in this workspace on 2026-06-15: create_project, upload_design_md, create_design_system_from_design_md, list_design_systems, and apply_design_system. This 2026-07-29 source refresh did not re-verify a broader live MCP surface. Do not claim list_projects, list_screens, get_project, get_screen, generate_screen_from_text, edit_screens, or generate_variants were used unless the current host exposes those exact tools in the active tool list.
Anti-Patterns
- Claiming a Stitch screen-generation, screen-editing, or screen-retrieval MCP call succeeded when the active host does not expose that tool.
- Uploading files, screenshots, HTML, markdown, or design assets to Stitch without user-approved destination and artifact details.
- Reading, printing, storing, or committing Stitch API keys, MCP config secrets, cookies, or credential-bearing files.
- Treating generated design or code as final without local render, syntax, or artifact verification.
- Collapsing this workflow into a broader frontend/design skill when Stitch-specific files, project IDs, or design-system assets matter.
Verification Protocol
Before claiming this skill was applied successfully:
- Pass/fail: Every component has typed props or an explicit reason it has no props.
- Pass/fail: Static content is separated from component structure.
- Pass/fail: Generated project code does not carry irrelevant upstream license headers.
- Pass/fail: The rendered app was checked locally or the blocker is documented.
- Pressure-test scenario: Repeat the workflow with Stitch MCP screen tools unavailable and confirm the fallback path remains honest and actionable.
- Success metric: The user can identify the exact artifact, project/design-system target, and verification evidence without relying on unstated MCP behavior.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/stitch-react-components and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Stitch MCP
- Fallback prompt: "Use the Stitch React Components skill without Stitch MCP. Use local Stitch exports and browser screenshots when MCP screen retrieval is unavailable. Show the exact files, commands, manual Stitch UI steps, and verification evidence used before concluding."
- Verified Stitch MCP tools in this workspace are design-system/project oriented; use broader screen tools only when the current host exposes them.
- Use local scripts, exported HTML/screenshots, the Stitch web UI, and project metadata files as the fallback evidence path.
Related Skills
