stitch-vue-vant-components
Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).
Best use case
stitch-vue-vant-components is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).
Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "stitch-vue-vant-components" skill to help with this workflow task. Context: Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/stitch-vue-vant-components/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How stitch-vue-vant-components Compares
| Feature / Agent | stitch-vue-vant-components | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Stitch to Vue 3 + Vant 4 Components **Constraint**: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to **Vue 3 + Vant 4** (Vite, .vue SFC, mobile-first). You are a **frontend engineer** turning Stitch designs into clean, modular Vue 3 + Vant 4 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 - **Vant (Vue 3)**: [Official](https://vant-ui.github.io/) · [Guide / Components (zh-CN)](https://vant-ui.github.io/vant/#/zh-CN) · [GitHub](https://github.com/youzan/vant) - Full links and usage: [references/official.md](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 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). - **Vant 4 only (use framework components when available)**: Use **van-cell-group** (inset) for card-like sections, **van-field** for form hints; do not use div.card or custom .card-header/.tips-text. Use `<van-*>` components per [references/contract.md](references/contract.md); mobile-first (375px base), safe area, flex layout. - **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 Vant 4 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 (mobile viewport). ## 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-vant** constraints, map to Vue SFC and Vant 4 components. If converting from Stitch HTML (e.g. get_screen htmlCode), use [references/tailwind-to-vant.md](references/tailwind-to-vant.md) for Tailwind utility → px/theme, then [references/contract.md](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 Vant tokens. ## Troubleshooting - **Fetch errors**: Quote the URL in the bash command; ensure `scripts/fetch-stitch.sh` is executable. - **Component mapping**: Follow [references/contract.md](references/contract.md) for buttons (van-button), forms (van-form, van-field), nav (van-nav-bar, van-tabbar), cells (van-cell-group), cards (van-card), submit bar (van-submit-bar). ## Keywords **English:** Stitch, Vue 3, Vant, Vant 4, Vite, mobile, van-button, van-nav-bar. **中文关键词:** Stitch、Vue 3、Vant、移动端、组件。 ## References - [Examples](examples/usage.md) - [Scripts](scripts/fetch-stitch.sh) - [Component index (per-component doc links)](references/component-index.md) - [Tailwind → Vant 4](references/tailwind-to-vant.md) — Tailwind utility → px/theme when converting Stitch HTML. - [Contract (Vant 4 mapping)](references/contract.md) - [Component API (props/events quick reference)](api/component-api.md) - [Official documentation](references/official.md) - [Architecture checklist](resources/architecture-checklist.md) - [Component template](resources/component-template.vue) - [Stitch API / MCP](https://stitch.withgoogle.com/docs/mcp/guide/)
Related Skills
vant-vue3
Provides structured guidance for Vant of Vue 3.0. Use when the user needs Vant with Vue 3, asks about mobile UI components such as Button, Cell, Form, Dialog, Toast, Popup, ConfigProvider, theme customization, project setup, or wants to implement mobile-first interfaces with vant or van- components.
stitch-vue-layui-components
Convert Stitch designs into modular Vite + Vue 3 + Layui-Vue components. Use when the user mentions Layui conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Layui tokens (2px/4px radius), enforces Vue SFC structure with Layui-Vue components (layui-btn, layui-input, lay-card, lay-page-header).
stitch-vue-element-components
Convert Stitch designs into modular Vite + Vue 3 + Element Plus components. Use when the user mentions Element Plus, element-ui, or Vue Desktop conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Element Plus tokens, enforces Vue SFC structure with el-* components (el-button, el-form, el-table, el-card, el-menu).
stitch-vue-bootstrap-components
Convert Stitch designs into modular Vite + Vue 3 + BootstrapVue/BootstrapVueNext components. Use when the user mentions Bootstrap or BootstrapVue conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Bootstrap utilities, enforces Vue SFC structure with Bootstrap components (b-container, b-row, b-col, b-button, b-card).
stitch-uviewpro-components
Convert Stitch designs into uni-app + Vue 3 + uView Pro pages and components. Use when the user mentions uView Pro, uviewpro, or uni-app Vue 3 conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to rpx/theme, enforces u-* component contracts (u-tabs, u-form, u-picker, u-card) with script setup.
stitch-uview-components
Convert Stitch designs into uni-app + Vue 2 + uView 2.0 pages and components. Use when the user mentions uView, uView 2, or uni-app Vue 2 conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to rpx/theme, enforces uni-app page structure with uView 2 u-* components (u-navbar, u-form, u-button, u-cell-group).
stitch-ui-prompt-architect
Build Stitch-ready prompts from vague UI ideas (Path A) or from a Design Spec plus user request (Path B). Use when polishing a UI prompt before Stitch generation, improving a prompt that produced poor results, or merging a Design Spec with framework contracts (uView, Element Plus, Layui, Bootstrap, Vant) into a sectioned Context/Layout/Components prompt.
stitch-ui-designer
Master orchestrator for end-to-end Stitch UI design and generation. Use when the user asks to design, create, or make a UI screen using Stitch. Coordinates design spec generation, framework contract injection, prompt assembly, and MCP execution (create_project, generate_screen_from_text, get_screen) in a single workflow.
stitch-ui-design-variants
Generate alternative Stitch design variant prompts for A/B testing and creative exploration. Use when the user wants multiple style, layout, or content options for a Stitch screen. Takes a base Design Spec or prompt and produces 3 distinct variants (layout, style, or content variations).
stitch-ui-design-spec-vant
Vant 4 (Vue 3/Mobile) design spec for Stitch screen generation. Use when the user mentions Vant, vant4, or vant-ui in a Stitch design request. Outputs a hard-constraints prefix with Vant tokens (Primary #1989fa, van-button/van-field/van-nav-bar components, mobile-first 375px) or a CONTRACT_SELECTION_JSON_V1 selector.
stitch-ui-design-spec-uviewpro
uView Pro (uni-app/Vue 3) design spec for Stitch screen generation. Use when the user mentions uview-pro, uviewpro, or uview 3.0 in a Stitch design request. Outputs a hard-constraints prefix with uView Pro tokens (Primary #3c9cff, rpx units, u-button/u-form/u-navbar components, script setup) or a CONTRACT_SELECTION_JSON_V1 selector.
stitch-ui-design-spec-uview
uView 2.0 (uni-app/Vue 2) design spec for Stitch screen generation. Use when the user mentions uview, uview2, or u-view in a Stitch design request. Do NOT use for uView Pro requests. Outputs a hard-constraints prefix with uView 2 tokens (Primary #3c9cff, u-row/u-col/u-button components) or a CONTRACT_SELECTION_JSON_V1 selector.