Stitch to Vue 3 + Layui-Vue Components
Constraint: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to Vue 3 + Layui-Vue (Vite, .vue SFC).
You are a frontend engineer turning Stitch designs into clean, modular Vue 3 + Layui-Vue 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/Vue 3 project)
- 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.
Official Documentation
Retrieval and Networking
- Discover Stitch MCP prefix: Run
list_tools to find the prefix (e.g. mcp_stitch__stitch:).
- Fetch screen metadata: Call
[prefix]:get_screen with projectId and screenId (numeric IDs) to get design JSON, htmlCode.downloadUrl, screenshot.downloadUrl, dimensions, deviceType.
- High-reliability HTML download: AI fetch tools can fail on Google Cloud Storage URLs. Use Bash to run the skill script:
bash scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html"
Ensure the URL is quoted.
- Visual reference: Use
screenshot.downloadUrl to confirm layout and details.
Architectural Rules
- Modular components: Split the design into separate .vue files; avoid one giant SFC.
- Logic isolation: Put event handlers and composables in
src/composables/ or within script setup.
- Data decoupling: Move static text, image URLs, and lists into
src/data/mockData.js (or .ts).
- Layui-Vue only (use framework components when available): Use lay-card for cards, lay-divider for dividers; do not use div.card or custom .card-header/.tips-text. Use Layui-Vue components (lay-btn, lay-input, lay-card, lay-page-header, lay-result, etc.) per references/contract.md; follow Layui color tokens and radius (2px/4px).
- Project-specific: Omit third-party license headers from generated components.
Execution Steps
- Environment: If the project has no
node_modules, run npm install.
- Data layer: Create
src/data/mockData.js from the design content.
- Component drafting: Use
resources/component-template.vue as base; replace placeholder with real component name and Layui-Vue tags per contract.
- Wiring: Update the app entry (e.g.
App.vue or router) to render the new components.
- Quality check: Verify against
resources/architecture-checklist.md; run npm run dev to confirm visually.
Integration with This Repo
- Get screen: Use stitch-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 spec: If Stitch was generated with stitch-ui-design-spec-layui constraints, map to Vue SFC and Layui-Vue components. If converting from Stitch HTML (e.g. get_screen htmlCode), use references/tailwind-to-layui.md for Tailwind utility → px/theme (radius 2px/4px only), then references/contract.md for component API.
- Design system: If the project has DESIGN.md (from stitch-design-md), align colors and spacing with that system when mapping to Layui tokens.
Troubleshooting
- Fetch errors: Quote the URL in the bash command; ensure
scripts/fetch-stitch.sh is executable.
- Component mapping: Follow references/contract.md for buttons (layui-btn), inputs (layui-input), cards (layui-card), tables (layui-table), page-header, result, skeleton, timeline, space.
Keywords
English: Stitch, Vue 3, Layui, Layui-Vue, Vite, layui-btn, lay-card.
中文关键词： Stitch、Vue 3、Layui、组件。
References
能力边界
✅ 适用场景
- 当你需要使用此技能对应的技术栈时
- 当项目需要遵循最佳实践时
- 当需要快速上手或深入理解核心概念时
⚠️ 需要注意
- 复杂业务逻辑需要结合具体场景调整
- 性能优化需要根据实际数据量评估
❌ 不适用场景
常见陷阱 (Gotchas)
- 版本兼容性：注意框架版本与依赖库的兼容性，不同版本 API 可能有差异
- 配置文件格式：配置文件格式错误是最常见的问题，建议使用编辑器的语法检查
- 环境变量：确保所有必要的环境变量已正确设置，敏感信息不要硬编码
- 依赖冲突：多版本共存时注意依赖冲突，使用 lock 文件锁定版本
- 性能陷阱：大数据量场景下注意性能优化，避免 N+1 查询等常见问题
使用流程
Step 1: 环境准备
确保开发环境已安装必要的依赖和工具。
Step 2: 配置初始化
根据项目需求进行基础配置。
Step 3: 核心功能使用
按照示例代码实现核心功能。
Step 4: 测试验证
运行测试确保功能正常。
Step 5: 部署上线
完成开发后进行部署和监控。