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

• Layui-Vue: Official (zh-CN) · Guide · Components · GitHub
• Full links and usage: references/official.md

Retrieval and Networking

1. Discover Stitch MCP prefix: Run

   list_tools

   to find the prefix (e.g.

   mcp_stitch__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 scripts/fetch-stitch.sh "<htmlCode.downloadUrl>" "temp/source.html"
   

   Ensure the URL is quoted.
4. 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

1. Environment: If the project has no

   node_modules

   , run

   npm install

   .
2. Data layer: Create

   src/data/mockData.js

   from the design content.
3. Component drafting: Use

   resources/component-template.vue

   as base; replace placeholder with real component name and Layui-Vue tags per contract.
4. Wiring: Update the app entry (e.g.

   App.vue

   or router) to render the new components.
5. 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.

Example: Stitch HTML to Layui-Vue SFC

Stitch HTML with Tailwind card:

<div class="bg-white rounded shadow p-4"><h2 class="text-lg font-bold">Dashboard</h2><button class="bg-teal-600 text-white px-4 py-2">Submit</button></div>

Converted Layui-Vue component:

<template>
  <lay-card title="Dashboard">
    <lay-btn type="normal">Submit</lay-btn>
  </lay-card>
</template>

Key mapping:

div.rounded.shadow

becomes

<lay-card>

, raw

<button>

becomes

<lay-btn>

, Tailwind radius maps to Layui 2px classic radius per references/contract.md.

References

• Examples
• Scripts
• Component index (per-component doc links)
• Tailwind → Layui-Vue — Tailwind utility → px/theme (2px/4px radius) when converting Stitch HTML.
• Contract (Layui-Vue mapping)
• Component API (props/events quick reference)
• Official documentation
• Architecture checklist
• Component template
• Stitch API / MCP