stitch-react-components

Convert Stitch design screens into modular React components with TypeScript props.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @swc/core, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It converts Stitch design screens into modular, theme-consistent React components so you avoid manual, error-prone redevelopment and styling drift.

Core Features & Use Cases

  • Design retrieval and resilient downloading: Fetches Stitch screen HTML and screenshots via the Stitch MCP namespace, using a system-level fetch script to handle GCS redirect/TLS issues.
  • Architecture-compliant component scaffolding: Generates components as modular files aligned to an Atomic Design structure, with logic isolated into hooks and data moved into a mock data layer.
  • Quality gates for safety and correctness: Runs an AST-based validator to enforce TypeScript Readonly props interfaces and prevent hardcoded hex styling, then checks against an architecture checklist.

Quick Start

Prompt the agent: "Convert my Landing Page screen in my Podcast Stitch Project to a React component system."

Frequently Asked Questions about stitch-react-components

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

FAQPage Schema
How do I convert Stitch design screens into React components?

To convert Stitch design screens into React components, this Skill fetches screen HTML via Stitch MCP calls and scaffolds modular React files. It maps extracted Tailwind theme values to a local style guide while wiring the output directly into a Vite/React app.

How does AST validation prevent hardcoded hex colors in generated React components?

AST validation prevents hardcoded hex colors by running an AST-based validator that enforces TypeScript Readonly props interfaces and blocks inline hex styling. This quality gate ensures generated React components rely strictly on mapped Tailwind theme values for visual fidelity.

Can I use this to extract Tailwind theme values from Stitch HTML for a Vite app?

Yes, you can extract Tailwind theme values from Stitch HTML for a Vite app. The Skill fetches Stitch HTML, extracts the theme values, and maps those styles to your local style guide before scaffolding the React components into your Vite project.

What's the best way to scaffold React components following Atomic Design from design screens?

The best way to scaffold React components following Atomic Design from design screens is using an automated generator that isolates logic into hooks and data into a mock layer. This Skill aligns generated modular files to Atomic Design structures for safe frontend code generation.

Why does fetching Stitch screen HTML fail with TLS or GCS redirect issues?

Fetching Stitch screen HTML can fail with TLS or GCS redirect issues during standard MCP retrieval. This Skill resolves these network fetching errors by using a system-level fetch script to reliably download Stitch HTML and screenshots.

Do I need a local TypeScript style guide before converting Stitch designs?

You do not need a pre-existing local TypeScript style guide before converting Stitch designs. The Skill extracts Tailwind theme values from the Stitch screens and maps the styles to your local environment, enforcing TypeScript Readonly props interfaces during component scaffolding.