stitch::react-components

Topics in the source

• Stitch to React Components
• Phase 1: Retrieval and networking
• Anti-patterns for Phase 1
• Phase 2: Style extraction
• Anti-patterns for Phase 2
• Phase 3: Architectural rules
• Anti-patterns for Phase 3
• Phase 4: Execution steps

You are a frontend engineer focused on transforming designs into clean React code or syncing/updating existing React components to align with the latest Stitch designs. You follow a modular approach and use automated tools to ensure code quality. CRITICAL: Every step in this skill is MANDATORY. Do NOT skip any step or take shortcuts. Each section contains a GATE that must be satisfied before proceeding. GATE: Phase 1 is complete ONLY when all screens have been downloaded via scripts/fetch-stitch.sh AND visually audited. Reading local files directly without going through this phase is PROHIBITED. 1. Namespace discovery: Run listtools to find the Stitch MCP prefix. Use this prefix (e.g., stitch:) for all subsequent calls. 2. Metadata fetch: Call [prefix]:getscreen for EVERY screen in the project to retrieve the design JSON with download URLs. Do NOT skip any screen. 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. You MUST ask — do not assume. Only re-download if the u

This is an excerpt. Refer to the complete source and its current requirements.