skills/stitch-skills/stitch-react-components/SKILL.md
Convert Stitch designs into modular Vite/React components with validation and design token consistency. Uses Stitch MCP get_screen to retrieve design JSON and HTML; supports high-reliability fetch via scripts; enforces modular structure, type safety, and theme-mapped Tailwind.
npx skillsauth add partme-ai/full-stack-skills stitch-react-componentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Constraint: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to React (Vite/React, TypeScript).
You are a frontend engineer turning Stitch designs into clean, modular React code. Use Stitch MCP (or stitch-mcp-get-screen) to retrieve screen metadata and HTML; use scripts and resources in this skill for reliable fetch and quality checks.
node-id query). (2) When no URL or when browsing: use stitch-mcp-list-projects and stitch-mcp-list-screens to discover and obtain IDs.list_tools to find the prefix (e.g. mcp_stitch__stitch:).[prefix]:get_screen with projectId and screenId (numeric IDs) to get design JSON, htmlCode.downloadUrl, screenshot.downloadUrl, dimensions, deviceType.bash scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html"
This uses curl -L for redirects and TLS. Ensure the URL is quoted.screenshot.downloadUrl to confirm layout and details.src/hooks/.src/data/mockData.ts.Readonly TypeScript interface [ComponentName]Props.tailwind.config from HTML <head>; sync with resources/style-guide.json if present; use theme-mapped Tailwind classes instead of raw hex.node_modules, run npm install so validation (if used) works.src/data/mockData.ts from the design content.resources/component-template.tsx as base; replace all StitchComponent with the real component name.App.tsx) to render the new components.npm run validate <file_path> if the project has a validate script; verify against resources/architecture-checklist.md; run npm run dev to confirm visually.get_screen) with projectId and screenId. Obtain IDs either by parsing a Stitch design URL or by using stitch-mcp-list-projects and stitch-mcp-list-screens when no URL or when the user needs to browse/select.scripts/fetch-stitch.sh is executable.references/architecture-checklist.md.English: Stitch, React, Vite, components, validation, mockData, Tailwind.
中文关键词: Stitch、React、组件、校验、Tailwind。
development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.