This skill turns screens from a Google Stitch project into a React codebase. It downloads each screen’s HTML and screenshot through the Stitch MCP server, pulls the Tailwind tokens out of the page head, and writes modular components with typed props, hooks and mock data.
It also works as a sync tool: when the Stitch project changes, it refreshes the local design files and updates the matching components. A validation script checks every component for a Props interface before the work counts as done.
What You Get
- A src/components folder with one file per reusable pattern such as cards, badges and search bars
- Custom hooks in src/hooks that hold event handlers and logic
- A src/data/mockData.ts file that holds all static text, image URLs and lists
- A resources/style-guide.json synced to the Tailwind config of the current Stitch project
- A .stitch/metadata.json file with project ID, device type, screens and last sync time
Common Use Cases
- Converting a freshly designed Stitch project into a Vite and React app
- Syncing an existing React app to the newest Stitch screen updates
- Wiring multi-page navigation with React Router links in place of href placeholders
What Makes It Unique
Every phase ends in a gate the agent has to satisfy before it moves on. Screens are always fetched through get_screen and a download script, the style guide is rewritten from the current project, and each component needs an exported-style Props interface that the bundled validator checks.
Under The Hood
The skill calls the Stitch MCP tools to read project and screen metadata, then runs a bundled shell script that downloads the HTML and screenshot files from Google Cloud Storage URLs. It reads and writes files in the working project, runs npm install when needed, and on request runs the validate script, tsc and the dev server. Validation and dev server steps wait for the user’s permission.