full-stack-skills/stitch-skills

stitch-ui-design-spec-uview

uView 2 design spec for Stitch. Outputs hard-constraints prefix or selector JSON and assembled prompt.

First seen Jun 23, 2026

Installation

$ npx skills add full-stack-skills/stitch-skills --skill stitch-ui-design-spec-uview

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from full-stack-skills/stitch-skills · top by installs.

npx skills add full-stack-skills/stitch-skills

Browse all from full-stack-skills/stitch-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsstitch*:*, Read, Write

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,257 B
  • docs SUMMARY.md 137 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 21 installs

SKILL.md

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

  • [Contract](references/contract.md)
  • [Examples](references/examples.md)
  • [Official Docs](references/official.md)

能力边界

✅ 适用场景

  • 当你需要使用此技能对应的技术栈时
  • 当项目需要遵循最佳实践时
  • 当需要快速上手或深入理解核心概念时

⚠️ 需要注意

  • 复杂业务逻辑需要结合具体场景调整
  • 性能优化需要根据实际数据量评估

❌ 不适用场景

  • 不相关的技术栈或框架
  • 需要完全自定义的特殊场景

常见陷阱 (Gotchas)

  1. 版本兼容性:注意框架版本与依赖库的兼容性,不同版本 API 可能有差异
  2. 配置文件格式:配置文件格式错误是最常见的问题,建议使用编辑器的语法检查
  3. 环境变量:确保所有必要的环境变量已正确设置,敏感信息不要硬编码
  4. 依赖冲突:多版本共存时注意依赖冲突,使用 lock 文件锁定版本
  5. 性能陷阱:大数据量场景下注意性能优化,避免 N+1 查询等常见问题

使用流程

Step 1: 环境准备

确保开发环境已安装必要的依赖和工具。

Step 2: 配置初始化

根据项目需求进行基础配置。

Step 3: 核心功能使用

按照示例代码实现核心功能。

Step 4: 测试验证

运行测试确保功能正常。

Step 5: 部署上线

完成开发后进行部署和监控。