stitch-ui-uview2-components

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 · Guide / Demo · 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: Construct name: projects/{project}/screens/{screen} from the string ID segments and call [prefix]:get_screen 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-contract-uview2 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).

Keywords

English: Stitch, uni-app, uView, uView 2, Vue 2, u-button, u-navbar.
Chinese keywords: Stitch, uni-app, uView, uView 2, components.

References

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

When to use

Load this skill when the user needs to select and execute a verifiable, recoverable professional workflow for the current request . First extract the goal, inputs, constraints, delivery format, and acceptance criteria from the request; the description summary is: Convert Stitch designs into uni-app and Vue 2 and uView 2.0 pages and components. Uses Stitch MCP get_screen for retrieval; high-reliability fetch via scripts; enforces uni-app page structure and uView 2 u-* component contracts.

Rules

• Read before write: first confirm the current state and real capabilities, then perform actions that change external state.
• Least privilege: use only the files, tools, accounts, and network scope required to complete the current step.
• Evidence first: when run results, resource IDs, versions, hashes, or test outputs are missing, clearly mark them as NOT_VERIFIED。
• Idempotency first: retain request identifiers and phase state; when results are unclear, query first and do not retry blindly.
• Privacy and security: logs, examples, receipts, and error messages must not contain tokens, cookies, keys, or personally sensitive data.

Workflow

Step 1: Clarify intent

Confirm whether this skill matches the goal; if it is only an adjacent need, hand it off to a more precise skill.

Step 2: Run prechecks

Confirm the goal, inputs, constraints, available tools, success criteria, and failure boundaries; if any critical condition is unknown, stop at the read-only stage.

Step 3: Form a plan

List the tools to be called, the objects that will change, the success criteria, and the safe exit method after failure.

Step 4: Execute actions

Execute in the smallest sufficient steps, and record evidence at key state changes; retain a traceable status or receipt for every external call.

Step 5: Verify delivery

Output results, verification evidence, unfinished items, risks, and clear next steps, and state facts, inferences, and unverified items separately.

Validation checklist

• The skill trigger conditions are consistent with the user's intent, and adjacent tasks have not been misrouted to this skill.
• Inputs, target objects, versions, and output locations are all clear, and no guessed values have been used in place of required values.
• All write, paid, publish, or irreversible actions are within the scope authorized by the user.
• Results have been verified with independent checks; "command succeeded" or "file exists" alone does not count as complete acceptance.
• The output includes actual evidence, failed/skipped items, remaining risks, and executable next steps.

Gotchas

1. Treating a plan as a result: documentation or prompts are not the same as actual execution; the actual level of execution must be stated.
2. Erroneous retry: a timeout or lost response may already have produced a remote state; query first, then decide whether to retry.
3. Implicit scope expansion: batch, full-scale, publish, overwrite, and paid actions are not natural extensions of ordinary reads and writes.
4. Version drift: when referencing external resources, record the version, tag, or commit; do not treat a mutable branch as release evidence.
5. Stale evidence: caches, old screenshots, and historical tests cannot prove the current environment; refresh key evidence before delivery.

Non-applicability and boundaries

Do not exceed the scope given by the user; writing, payment, publishing, and irreversible actions require explicit authorization. If the request requires another skill, do not copy its content; hand off by skill name and preserve the current task context.

Progressive disclosure

• When input/output, state, and authorization points need to be determined, read references/workflow-contract.md。
• When pre-delivery self-check is needed, read references/validation-checklist.md。
• When encountering timeouts, partial success, or recovery scenarios, read references/error-recovery.md。
• For first run, privilege escalation refusal, and failure recovery, refer respectively to examples/happy-path.md、examples/boundary-refusal.md、examples/failure-recovery.md。