OpenSkillIndex← back to search
claude-codedevelopment

Full-stack-skills 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).

install
source · Clone the upstream repo
git clone https://github.com/partme-ai/full-stack-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/stitch-skills/stitch-uview-components" ~/.claude/skills/partme-ai-full-stack-skills-stitch-uview-components && rm -rf "$T"
manifest: skills/stitch-skills/stitch-uview-components/SKILL.md
tags
#stitch-conversion#uni-app#uview-2#vue-2#design-to-code
source content

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

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 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. 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 for Tailwind utility → rpx/theme, 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 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 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:

<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:

<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