SkillsAdd

full-stack-skills/stitch-skills

stitch-react-components

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.

First seen Jun 23, 2026

Installation

$ npx skills add full-stack-skills/stitch-skills --skill stitch-react-components
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
vercel-composition-patterns Shared topics
vercel-labs/agent-skills 326.5K installs
vercel-react-native-skills Shared topics
vercel-labs/agent-skills 205.5K installs
react:components Similar name
google-labs-code/stitch-skills

Converts Stitch designs into modular Vite and React components using system-level networking an…

50.7K installs
building-components Similar name
vercel/components.build

Guide for building modern, accessible, and composable UI components. Use when building new comp…

12.5K installs

Also in this package

Other skills from full-stack-skills/stitch-skills · top by installs.

npx skills add full-stack-skills/stitch-skills
stitch-ui-design-spec-element-plus 24 stitch-ui-design-spec-generator 23 stitch-design-md 23 stitch-ui-prompt-architect 22 stitch-ui-designer 22 stitch-ui-design-spec-layui 22 stitch-vue-element-components 22 stitch-ui-design-spec-bootstrap 22 stitch-ued-guide 22 stitch-shadcn-ui 22

Browse all from full-stack-skills/stitch-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsstitch*:*, Bash, Read, Write, web_fetch

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,260 B
  • docs SUMMARY.md 308 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 22 installs

SKILL.md

Stitch to React Components

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.

Prerequisites

  • Stitch MCP Server (https://stitch.withgoogle.com/docs/mcp/guide/)
  • Node.js and npm (for Vite/React project and optional validation)
  • Stitch project and screen IDs — two ways: (1) From a Stitch design URL: parse projectId (path) and screenId (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.

Retrieval and Networking

  1. Discover Stitch MCP prefix: Run listtools to find the prefix (e.g. mcpstitch__stitch:).
  2. Fetch screen metadata: Call [prefix]:get_screen with projectId and screenId (numeric IDs) to get design JSON, htmlCode.downloadUrl, screenshot.downloadUrl, dimensions, deviceType.
  3. High-reliability HTML download: AI fetch tools can fail on Google Cloud Storage URLs. Use Bash to run the skill script:

``bash bash scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html" ` This uses curl -L` for redirects and TLS. Ensure the URL is quoted.

  1. Visual reference: Use screenshot.downloadUrl to confirm layout and details.

Architectural Rules

  • Modular components: Split the design into separate files; avoid one giant file.
  • Logic isolation: Put event handlers and business logic in src/hooks/.
  • Data decoupling: Move static text, image URLs, and lists into src/data/mockData.ts.
  • Type safety: Every component must have a Readonly TypeScript interface [ComponentName]Props.
  • Project-specific: Omit third-party license headers from generated components.
  • Style mapping: Extract tailwind.config from HTML <head>; sync with resources/style-guide.json if present; use theme-mapped Tailwind classes instead of raw hex.

Execution Steps

  1. Environment: If the project has no node_modules, run npm install so validation (if used) works.
  2. Data layer: Create src/data/mockData.ts from the design content.
  3. Component drafting: Use resources/component-template.tsx as base; replace all StitchComponent with the real component name.
  4. Wiring: Update the app entry (e.g. App.tsx) to render the new components.
  5. Quality check: Run 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.

Integration with This Repo

  • Get screen: Use stitch-mcp-get-screen (or MCP 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.
  • Design system: If the project has DESIGN.md (from stitch-design-md), align colors and typography with that semantic system when mapping to Tailwind. When converting Stitch HTML to React, use [references/tailwind-to-react.md](references/tailwind-to-react.md) for theme-mapped Tailwind (tokens → tailwind.config); keep Tailwind classes in output, map Stitch tokens to project theme.

Troubleshooting

  • Fetch errors: Quote the URL in the bash command to avoid shell issues; ensure scripts/fetch-stitch.sh is executable.
  • Validation errors: Fix missing Props interfaces and hardcoded styles per the AST report; follow references/architecture-checklist.md.

Keywords

English: Stitch, React, Vite, components, validation, mockData, Tailwind. 中文关键词： Stitch、React、组件、校验、Tailwind。

References

  • Examples: [examples/usage.md](examples/usage.md)
  • Style Mapping: [references/tailwind-to-react.md](references/tailwind-to-react.md) — Theme-mapped Tailwind when converting Stitch HTML; keep Tailwind classes, sync Stitch tokens to tailwind.config.
  • Resources:

- [resources/architecture-checklist.md](resources/architecture-checklist.md) - [resources/component-template.tsx](resources/component-template.tsx)

能力边界

✅ 适用场景

  • 当你需要使用此技能对应的技术栈时
  • 当项目需要遵循最佳实践时
  • 当需要快速上手或深入理解核心概念时

⚠️ 需要注意

  • 复杂业务逻辑需要结合具体场景调整
  • 性能优化需要根据实际数据量评估

❌ 不适用场景

  • 不相关的技术栈或框架
  • 需要完全自定义的特殊场景

常见陷阱 (Gotchas)

  1. 版本兼容性：注意框架版本与依赖库的兼容性，不同版本 API 可能有差异
  2. 配置文件格式：配置文件格式错误是最常见的问题，建议使用编辑器的语法检查
  3. 环境变量：确保所有必要的环境变量已正确设置，敏感信息不要硬编码
  4. 依赖冲突：多版本共存时注意依赖冲突，使用 lock 文件锁定版本
  5. 性能陷阱：大数据量场景下注意性能优化，避免 N+1 查询等常见问题

使用流程

Step 1: 环境准备

确保开发环境已安装必要的依赖和工具。

Step 2: 配置初始化

根据项目需求进行基础配置。

Step 3: 核心功能使用

按照示例代码实现核心功能。

Step 4: 测试验证

运行测试确保功能正常。

Step 5: 部署上线

完成开发后进行部署和监控。