stitch-uview-components
$
npx mdskill add partme-ai/full-stack-skills/stitch-uview-componentsConverts Stitch designs into uni-app Vue 2 pages using uView 2.0 components when users mention uView or uni-app conversion.
- Helps developers transform Stitch design screens into functional uni-app Vue 2 code with uView 2.0 components.
- Integrates with Stitch MCP for screen retrieval and uses Bash, Read, Write, and web_fetch tools.
- Activates only when users explicitly mention Stitch and uni-app Vue 2 uView 2.0 conversion.
- Delivers clean, modular .vue files with u-* components like u-navbar and u-form for direct use.
SKILL.md
.github/skills/stitch-uview-componentsView on GitHub ↗
---
name: stitch-uview-components
description: "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)."
allowed-tools: "stitch*:*, Bash, Read, Write, web_fetch"
---
# Stitch to uni-app + uView 2.0 Components
**Constraint**: Only use this skill when the user explicitly mentions "Stitch" and converting Stitch screens to **uni-app + Vue 2 + uView 2.0** (pages/, components/, .vue, u-* components).
You are a **frontend engineer** turning Stitch designs into clean, modular uni-app + uView 2 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/)
- uni-app / HBuilderX or Vue CLI for uni-app (Vue 2)
- 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
- **uView 2.0 (Vue 2)**: [Official](https://www.uviewui.com/) · [Guide / Demo](https://www.uviewui.com/guide/demo.html) · [Components](https://www.uviewui.com/components/intro.html) · [GitHub](https://github.com/umicro/uView2.0)
- 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 pages/components**: Split the design into pages under `pages/` and shared components under `components/`; avoid one giant page.
- **Logic isolation**: Put event handlers and mixins/utils in appropriate modules.
- **Data decoupling**: Move static text, image URLs, and lists into `data/` or page data.
- **uView 2 only (use framework components when available)**: Use `u-*` components per [references/contract.md](references/contract.md). Card-like blocks → **u-cell-group** + **u-cell** or **u-text**; hints/tips → **u-text**; dividers → **u-line** / **u-divider**. Do not use view/text + custom class (.card, .card-title, .label-optional, .tips-text, .unit).
- **Project-specific**: Omit third-party license headers from generated pages/components.
## Execution Steps
1. **Environment**: Ensure uni-app project has uView 2 installed and configured (main.js, uni.scss).
2. **Data layer**: Create or update data sources (e.g. `data/mockData.js`) from the design content.
3. **Page drafting**: Use `resources/page-template.vue` as base; replace placeholder with real page name and uView 2 tags per contract.
4. **Wiring**: Register pages in `pages.json`; add tabBar or navigation as needed.
5. **Quality check**: Verify against `resources/architecture-checklist.md`; run in HBuilderX or CLI to confirm on simulator/device.
## 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-uview** constraints, map to uni-app pages and uView 2 components. If converting from Stitch HTML (e.g. get_screen htmlCode), use [references/tailwind-to-uview.md](references/tailwind-to-uview.md) for Tailwind utility → rpx/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 uView 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 layout (u-row, u-col), forms (u-form, u-input), nav (u-navbar, u-tabs), list (u-swipe-action), feedback (u-toast, u-modal).
## Example: Stitch HTML to uView 2 Page
Stitch HTML with Tailwind card and button:
```html
<div class="bg-white rounded-lg shadow p-4"><h2 class="text-lg font-bold">Profile</h2><button class="bg-blue-500 text-white px-4 py-2 rounded">Save</button></div>
```
Converted uView 2 page:
```vue
<template>
<view class="page">
<u-navbar title="Profile" :autoBack="true" />
<u-cell-group>
<u-cell title="Profile" />
</u-cell-group>
<u-button type="primary" text="Save" @click="handleSave" />
</view>
</template>
```
Key mapping: `div.rounded-lg.shadow` becomes `<u-cell-group>`, raw `<button>` becomes `<u-button type="primary">`, Tailwind px maps to rpx.
## References
- [Examples](examples/usage.md)
- [Scripts](scripts/fetch-stitch.sh)
- [Component index (per-component doc links)](references/component-index.md)
- [Tailwind → uView 2](references/tailwind-to-uview.md) — Tailwind utility → rpx/theme when converting Stitch HTML.
- [Contract (uView 2 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)
- [Page template](resources/page-template.vue)
- [Stitch API / MCP](https://stitch.withgoogle.com/docs/mcp/guide/)
More from partme-ai/full-stack-skills
- adobe-xd"Guides creation of UI/UX designs, interactive prototypes, reusable components, and design specs in Adobe XD. Use when the user asks about Adobe XD artboards, prototype links, repeat grids, component states, design tokens export, or developer handoff."
- angular"Provides comprehensive guidance for Angular framework including components, modules, services, dependency injection, routing, forms, and TypeScript integration. Use when the user asks about Angular, needs to create Angular applications, implement Angular components, or work with Angular features."
- ansible"Provides comprehensive guidance for Ansible automation including playbooks, roles, inventory, and module usage. Use when the user asks about Ansible, needs to automate IT tasks, create Ansible playbooks, or manage infrastructure with Ansible."
- ant-design-mini"Builds mini-program UIs with Ant Design Mini components for Alipay and WeChat mini-programs. Covers Button, Form, List, Modal, Tabs, NavBar, and 60+ components with theme customization and CSS variable theming. Use when the user needs to create mini-program interfaces with Ant Design Mini, configure themes, or implement mini-program-specific UI patterns."
- ant-design-mobile"Builds React mobile UIs with Ant Design Mobile (antd-mobile) components including Button, Form, List, Modal, Picker, Tabs, PullToRefresh, InfiniteScroll, and 50+ mobile-optimized components. Use when the user needs to create mobile-first React interfaces, implement mobile navigation, forms, or data display with Ant Design Mobile."
- ant-design-react"Builds enterprise React UIs with Ant Design (antd) including 60+ components (Button, Form, Table, Select, Modal, Message), design tokens, TypeScript support, and ConfigProvider theming. Use when the user needs to create React applications with Ant Design, build forms with validation, display data tables, or customize the Ant Design theme."
- ant-design-vueProvides comprehensive guidance for Ant Design Vue (AntDV) component library for Vue 3. Covers installation, usage, API reference, templates, and all component categories. Use when building enterprise-class UI with Vue 3 and Ant Design.
- api-doc-generator"Generate API documentation by scanning Controller classes, extracting endpoint URLs, HTTP methods, parameters, and response structures, then producing standardized docs from templates. Use when the user explicitly mentions generating API documentation, creating API docs, scanning interfaces, or documenting REST APIs. Do not trigger for generic documentation requests without explicit API mention."
- appium"Provides comprehensive guidance for Appium mobile testing including mobile app automation, element location, gestures, and cross-platform testing. Use when the user asks about Appium, needs to test mobile applications, automate mobile apps, or write Appium test scripts."
- ascii-ansi-colorizer"Add an ANSI color layer to existing ASCII/plain-text output (gradient/rainbow/highlights) with alignment-safe rules and a required no-color fallback. Use when the user wants to colorize terminal output, add rainbow effects to CLI text, or style ASCII art with ANSI colors."