← ClaudeAtlas

react-componentslisted

Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.
aiskillstore/marketplace · ★ 329 · Web & Frontend · score 82
Install: claude install-skill aiskillstore/marketplace
# 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. **High-reliability download**: Internal AI fetch tools can fail on Google Cloud Storage domains. - Use the `Bash` tool to run: `bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" "temp/source.html"`. - This script handles the necessary redirects and security handshakes. 4. **Visual audit**: Check `screenshot.downloadUrl` to confirm the 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 w