What is stitch-react-components?

A frontend-engineering skill to convert Stitch designs into modular Vite/React components with type safety and Tailwind mapping.

What tooling does it rely on?

Stitch MCP get_screen, stitch-mcp-get-screen, a Bash fetch script for reliable HTML download, and a Node/Vite React project for development.

How are design tokens mapped to Tailwind?

Extract tailwind.config from the HTML head and synchronize with resources/style-guide.json, then apply theme-mapped Tailwind classes instead of raw tokens.

stitch-react-components

npx machina-cli add skill partme-ai/stitch-skills/stitch-react-components --openclaw

Files (1)

SKILL.md

4.8 KB

Stitch to React Components

Constraint: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to React (Vite/React, TypeScript).

You are a frontend engineer turning Stitch designs into clean, modular React code. Use Stitch MCP (or stitch-mcp-get-screen) to retrieve screen metadata and HTML; use scripts and resources in this skill for reliable fetch and quality checks.

Prerequisites

Stitch MCP Server (https://stitch.withgoogle.com/docs/mcp/guide/)
Node.js and npm (for Vite/React project and optional validation)
Stitch project and screen IDs — two ways: (1) From a Stitch design URL: parse projectId (path) and screenId (node-id query). (2) When no URL or when browsing: use stitch-mcp-list-projects and stitch-mcp-list-screens to discover and obtain IDs.

Retrieval and Networking

Discover Stitch MCP prefix: Run list_tools to find the prefix (e.g. mcp_stitch__stitch:).
Fetch screen metadata: Call [prefix]:get_screen with projectId and screenId (numeric IDs) to get design JSON, htmlCode.downloadUrl, screenshot.downloadUrl, dimensions, deviceType.
High-reliability HTML download: AI fetch tools can fail on Google Cloud Storage URLs. Use Bash to run the skill script:
```
bash scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html"
```
This uses curl -L for redirects and TLS. Ensure the URL is quoted.
Visual reference: Use screenshot.downloadUrl to confirm layout and details.

Architectural Rules

Modular components: Split the design into separate files; avoid one giant file.
Logic isolation: Put event handlers and business logic in src/hooks/.
Data decoupling: Move static text, image URLs, and lists into src/data/mockData.ts.
Type safety: Every component must have a Readonly TypeScript interface [ComponentName]Props.
Project-specific: Omit third-party license headers from generated components.
Style mapping: Extract tailwind.config from HTML <head>; sync with resources/style-guide.json if present; use theme-mapped Tailwind classes instead of raw hex.

Execution Steps

Environment: If the project has no node_modules, run npm install so validation (if used) works.
Data layer: Create src/data/mockData.ts from the design content.
Component drafting: Use resources/component-template.tsx as base; replace all StitchComponent with the real component name.
Wiring: Update the app entry (e.g. App.tsx) to render the new components.
Quality check: Run npm run validate <file_path> if the project has a validate script; verify against resources/architecture-checklist.md; run npm run dev to confirm visually.

Integration with This Repo

Get screen: Use stitch-mcp-get-screen (or MCP get_screen) with projectId and screenId. Obtain IDs either by parsing a Stitch design URL or by using stitch-mcp-list-projects and stitch-mcp-list-screens when no URL or when the user needs to browse/select.
Design system: If the project has DESIGN.md (from stitch-design-md), align colors and typography with that semantic system when mapping to Tailwind. When converting Stitch HTML to React, use references/tailwind-to-react.md for theme-mapped Tailwind (tokens → tailwind.config); keep Tailwind classes in output, map Stitch tokens to project theme.

Troubleshooting

Fetch errors: Quote the URL in the bash command to avoid shell issues; ensure scripts/fetch-stitch.sh is executable.
Validation errors: Fix missing Props interfaces and hardcoded styles per the AST report; follow references/architecture-checklist.md.

Keywords

English: Stitch, React, Vite, components, validation, mockData, Tailwind.
中文关键词： Stitch、React、组件、校验、Tailwind。

References

Examples: examples/usage.md
Style Mapping: references/tailwind-to-react.md — Theme-mapped Tailwind when converting Stitch HTML; keep Tailwind classes, sync Stitch tokens to tailwind.config.
Resources:
- resources/architecture-checklist.md
- resources/component-template.tsx
Scripts: scripts/fetch-stitch.sh
Stitch API / MCP

Source

git clone https://github.com/partme-ai/stitch-skills/blob/main/skills/stitch-react-components/SKILL.mdView on GitHub

Overview

Converts Stitch screens into modular Vite/React components with validation and design-token consistency. It uses Stitch MCP get_screen to fetch design JSON and HTML, enabling reliable assembly, type-safe interfaces, and theme-mapped Tailwind classes.

How This Skill Works

Stitch MCP get_screen retrieves design JSON, HTML, and assets using projectId and screenId. A high-reliability Bash script downloads the HTML to guard against storage URL failures, while visual checks confirm layout via the provided screenshot. The result is a split, modular codebase (src/components, src/hooks, src/data/mockData.ts) with Readonly props interfaces for type safety and theme-mapped Tailwind mapping.

When to Use It

Converting a Stitch screen into modular React components for a Vite/React project
Ensuring design-token consistency with theme-mapped Tailwind classes
Using Stitch MCP to reliably fetch screen JSON and HTML for validation
Breaking a Stitch screen into reusable components (e.g., Card, Button, List)
Setting up a data layer (mockData.ts) and type-safe ReadonlyProps for components

Quick Start

Step 1: Retrieve screen metadata with stitch-mcp-get-screen (projectId, screenId) to obtain design JSON and HTML URLs
Step 2: Download HTML reliably using the Bash script and begin scaffolding modular React components from the design
Step 3: Wire components into a Vite/React project, add a data layer (mockData.ts), and run validation (npm run validate) and dev server

Best Practices

Modularize components into small, single-purpose files per UI unit
Put event handlers and business logic in src/hooks to keep components clean
Move static text, image URLs, and lists into src/data/mockData.ts
Ensure every component has a Readonly [ComponentName]Props interface
Extract tailwind.config from HTML head and align with resources/style-guide.json

Example Use Cases

Split a Stitch screen into Card and Image components with Tailwind mappings
Refactor a Stitch form screen into isolated Form, Input, and Button components
Create a reusable List component from a Stitch List screen using data-driven items
Validate HTML rendering by running the high-reliability fetch script and comparing screenshots
Sync design tokens to tailwind.config via resources/style-guide.json for consistent theming

Frequently Asked Questions

Add this skill to your agents