Get the FREE Ultimate OpenClaw Setup Guide →

stitch-ui-design-spec-uview

npx machina-cli add skill partme-ai/stitch-skills/stitch-ui-design-spec-uview --openclaw
Files (1)
SKILL.md
2.9 KB

uView Design Spec (uView 2.0 / uni-app / Vue2)

Constraint: Only use this skill when the user explicitly mentions "Stitch".

Purpose

This skill makes the uView 2.0 design spec executable in two modes:

  1. Prefix mode: output a paste-ready Hard constraints prefix for Stitch [Context].
  2. Selector mode: output CONTRACT_SELECTION_JSON_V1 and then an assembled Stitch prompt that injects only the required component/state snippets.

Trigger Keywords

Prefer this skill when the user request includes any of:

  • uview, uview2, uview2.0, u-view

Negative Constraint: If the user says "uView Pro" or "uviewpro", DO NOT use this skill. Use stitch-ui-design-spec-uviewpro instead.

Chinese trigger keywords (only for triggering):

  • uview 风格
  • 美化
  • 优化

Source of Truth

  • references/contract.md
  • references/examples.md
  • references/official.md

Output (STRICT)

Decide the mode by the user intent:

  • If the user asks for beautify/polish/refine an existing screen, or asks for selector / JSON / contracts.include / states.include → use Selector mode.
  • Otherwise → use Prefix mode.

Prefix mode

Return exactly one code block:

[Hard constraints prefix]
- Framework: uView 2.0 (uni-app / Vue 2).
- Design Tokens:
  - Colors: Primary=#3c9cff, Success=#5ac725, Warning=#f9ae3d, Error=#f56c6c, Info=#909399.
  - Background: #f3f4f6. Border: #dadbde.
  - Spacing: 4, 8, 12, 16, 20, 24, 32, 40 (px).
  - Radius: 8, 12, 999 (px).
- Component Contracts:
  - Layout: Use <u-row> and <u-col span="...">.
  - Forms: Use <u--form> (note double dash), <u--input border="surround">.
  - Buttons: Use <u-button type="primary">.
  - Navbar: Use <u-navbar title="..." :autoBack="true">.
  - List: <u-swipe-action>, <u-index-list>, <u-waterfall>.
  - Feedback: Use this.$refs.uToast.show({...}), <u-code> (SMS).
- Layout Invariants:
  - No gradients as default style.
  - Minimal shadows.
  - Transitions: 200ms ease-out.

Selector mode

Return exactly two code blocks, in this order, with no extra prose:

  1. Contract selection JSON:
{
  "version": "CONTRACT_SELECTION_JSON_V1",
  "designSystem": "uview2",
  "mode": "selector",
  "contracts": { "include": [] },
  "states": { "include": [] }
}
  1. Final Stitch prompt:
[Context]
(Paste Hard Constraints Prefix here)
(Add "Layout Invariants" from contract.md if beautifying)

[Layout]
(Describe the macro layout structure, e.g., "Mobile Column Layout with Navbar")

[Components]
(Inject component snippets matching the JSON selection above)

References

Source

git clone https://github.com/partme-ai/stitch-skills/blob/main/skills/stitch-ui-design-spec-uview/SKILL.mdView on GitHub

Overview

This skill generates Stitch-ready design specs for uView 2.0 (uni-app / Vue 2). It outputs either a hard-constraints prefix or a selector-style contract plus assembled prompt, ensuring consistent integration with Stitch workflows.

How This Skill Works

The tool analyzes user intent to decide between Prefix mode and Selector mode. In Prefix mode it returns a single hard-constraints prefix block ready to paste. In Selector mode it outputs a CONTRACT_SELECTION_JSON_V1 block followed by a final Stitch prompt that injects only the required component/state snippets.

When to Use It

  • When the user asks for a Stitch-ready uView 2 spec in prefix mode (hard constraints).
  • When the user wants to beautify/refine an existing screen and requests selector/JSON/contracts.include/states.include outputs.
  • When the user asks to output only the necessary component/state snippets (selector mode).
  • When you need a paste-ready, consistent design prompt using uView 2 components (e.g., u-row, u-navbar).
  • When preparing a Stitch prompt that should be pasted directly without extra prose.

Quick Start

  1. Step 1: Mention Stitch along with uView keywords (e.g., uview, uview2).
  2. Step 2: Decide your mode: Prefix for hard constraints, Selector for JSON + prompt.
  3. Step 3: Provide any layout or component requirements and generate the output.

Best Practices

  • Confirm the user intent (beautify/selectors) before generating output.
  • Use the uView 2.0 tokens exactly as specified (colors, spacing, radius).
  • Reference tokens and avoid introducing gradients or heavy shadows in constraints.
  • Keep the output strictly formatted for Stitch: one code block in Prefix mode or two blocks in Selector mode.
  • Test by pasting the generated output into Stitch to verify correct injection of components/state snippets.

Example Use Cases

  • Engineer requests a Prefix mode constraint for a new login screen using uView 2.
  • Designer wants a Selector mode output to assemble a dashboard with only required components.
  • Team wants to beautify a profile screen by generating contracts.include/state.include in selector mode.
  • Developer prepares a Stitch prompt to paste directly for a minimal List layout using u-view components.
  • Architect requires constraints with no gradients and a 200ms ease-out transition.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers