react:components

Convert Stitch screen designs into modular Vite React components with validated AST outputs.

1|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill react-components-svssdeva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react:components
Source: https://github.com/svssdeva/agentic-skills/tree/main/react/react-components
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill react-components-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, bash, list_tools, web_fetch, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you reliably convert Stitch design artifacts into modular, type-safe React components for a Vite project, reducing rework and layout/implementation drift.

Core Features & Use Cases

  • Stitch retrieval & networking: Discovers the Stitch tool prefix, fetches screen JSON, and downloads HTML and screenshots needed for implementation decisions.
  • Deterministic, validated component output: Uses project templates and enforces AST-based validation with npm run validate, ensuring each generated component meets quality rules.
  • Architecture-aligned React implementation: Separates hooks and logic, decouples static data into a mock data file, and maps Tailwind theme values to the project’s style guide.
  • Use Case: When you have a set of Stitch pages, generate a React component per page that matches the design while keeping business logic isolated and styling consistent with your Tailwind configuration.

Quick Start

Use the react:components skill to generate React components for a Stitch design page using the project’s validation and Tailwind style mapping rules.

Frequently Asked Questions about react:components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Stitch designs into React components with TypeScript and Tailwind?

To convert Stitch designs into React components, this tool fetches screen JSON and HTML artifacts to generate modular Vite components. It enforces TypeScript prop interfaces and maps Tailwind theme values to your project's style guide for consistent, type-safe output.

What's the best way to ensure generated React components match my Vite project's architecture?

To ensure generated React components match your Vite architecture, the tool isolates hook-based logic, decouples static data into mock files, and validates the component AST using npm run validate. This enforces structural consistency and reduces implementation drift.

Can I use this to generate React components from Stitch screens without manual styling adjustments?

Yes, you can generate React components from Stitch screens without manual styling adjustments. The tool synchronizes generated Tailwind classes with resources/style-guide.json, ensuring the output matches your design system's theme values automatically.

Does converting Stitch designs to React code require AST validation?

AST validation is required when converting Stitch designs to React code to guarantee each generated component meets project quality rules. The tool runs npm run validate against the output AST to catch structural errors and ensure the component is production-ready.

Why do my Stitch to React component generations include separate mock data files?

Stitch to React component generations include separate mock data files to decouple static design data from business logic. This keeps your React components modular and maintainable by isolating hook-based logic from the hardcoded content fetched from the design artifacts.

What dependencies do I need to generate React components from Stitch design pages?

To generate React components from Stitch design pages, you need npm and bash available to execute validation scripts and fetch design artifacts. The environment must support list_tools and web_fetch to retrieve the Stitch screen JSON, screenshots, and HTML needed for implementation.