Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
google-labs-code avatar

React:Components

  • 50.5k installs
  • 7.8k repo stars
  • Updated July 21, 2026
  • google-labs-code/stitch-skills

react:components is an agent skill that converts Stitch design files into modular Vite and React components using Stitch MCP networking.

About

react:components is a frontend engineering skill that transforms Stitch designs into clean, modular Vite and React components.

  • Automated namespace discovery and Stitch MCP tool detection
  • Metadata fetch via stitch:get_screen followed by conditional local cache check
  • High-reliability download scripts that handle Google Cloud Storage edge cases

React:Components by the numbers

  • 50,489 all-time installs (skills.sh)
  • +57 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #15 of 2,277 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
From the docs

What react:components says it does

--- name: react:components description: Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.
SKILL.md
npx skills add https://github.com/google-labs-code/stitch-skills --skill reactcomponents

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs50.5k
repo stars7.8k
Security audit2 / 3 scanners passed
Last updatedJuly 21, 2026
Repositorygoogle-labs-code/stitch-skills

How do you convert Stitch designs to React components?

Turn Stitch design files into production-ready, modular React and Vite components without manual translation.

Who is it for?

Frontend developers using Google Stitch designs who want automated, validated React component codegen.

Skip if: Projects without Stitch design sources or teams building UI purely by hand without a design-to-code pipeline.

When should I use this skill?

The user has Stitch designs and needs Vite/React components generated from screen metadata.

What you get

Modular Vite and React component files generated from Stitch screen metadata with AST validation.

  • Modular React components
  • Vite-compatible module files
  • AST-validated component source

Files

SKILL.mdMarkdownGitHub ↗

Stitch to React Components

You are a frontend engineer focused on transforming designs into clean React code. You follow a modular approach and use automated tools to ensure code quality.

Retrieval and networking

1. Namespace discovery: Run list_tools to find the Stitch MCP prefix. Use this prefix (e.g., stitch:) for all subsequent calls. 2. Metadata fetch: Call [prefix]:get_screen to retrieve the design JSON. 3. Check for existing designs: Before downloading, check if .stitch/designs/{page}.html and .stitch/designs/{page}.png already exist:

  • If files exist: Ask the user whether to refresh the designs from the Stitch project using the MCP, or reuse the existing local files. Only re-download if the user confirms.
  • If files do not exist: Proceed to step 4.

4. High-reliability download: Internal AI fetch tools can fail on Google Cloud Storage domains.

  • HTML: bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" ".stitch/designs/{page}.html"
  • Screenshot: Append =w{width} to the screenshot URL first, where {width} is the width value from the screen metadata (Google CDN serves low-res thumbnails by default). Then run: bash scripts/fetch-stitch.sh "[screenshot.downloadUrl]=w{width}" ".stitch/designs/{page}.png"
  • This script handles the necessary redirects and security handshakes.

5. Visual audit: Review the downloaded screenshot (.stitch/designs/{page}.png) to confirm design intent and layout details.

Architectural rules

  • Modular components: Break the design into independent files. Avoid large, single-file outputs.
  • Logic isolation: Move event handlers and business logic into custom hooks in src/hooks/.
  • Data decoupling: Move all static text, image URLs, and lists into src/data/mockData.ts.
  • Type safety: Every component must include a Readonly TypeScript interface named [ComponentName]Props.
  • Project specific: Focus on the target project's needs and constraints. Leave Google license headers out of the generated React components.
  • Style mapping:
  • Extract the tailwind.config from the HTML <head>.
  • Sync these values with resources/style-guide.json.
  • Use theme-mapped Tailwind classes instead of arbitrary hex codes.

Execution steps

1. Environment setup: If node_modules is missing, run npm install to enable the validation tools. 2. Data layer: Create src/data/mockData.ts based on the design content. 3. Component drafting: Use resources/component-template.tsx as a base. Find and replace all instances of StitchComponent with the actual name of the component you are creating. 4. Application wiring: Update the project entry point (like App.tsx) to render the new components. 5. Quality check:

  • Run npm run validate <file_path> for each component.
  • Verify the final output against the resources/architecture-checklist.md.
  • Start the dev server with npm run dev to verify the live result.

Troubleshooting

  • Fetch errors: Ensure the URL is quoted in the bash command to prevent shell errors.
  • Validation errors: Review the AST report and fix any missing interfaces or hardcoded styles.

Related skills

Forks & variants (1)

React:Components has 1 known copy in the catalog totaling 54 installs. They canonicalize to this original listing.

How it compares

Use react:components when the source of truth is Stitch design JSON; use hand-authored component skills when no Stitch MCP pipeline exists.

FAQ

What tools does react:components use?

react:components discovers the Stitch MCP prefix, calls get_screen for design JSON, and uses Bash, Read, Write alongside stitch*:* tools to emit validated Vite and React components.

How does react:components ensure code quality?

react:components applies AST-based validation after codegen so generated React modules follow project structure and remain composable.

Is React:Components safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Frontend Developmentfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.