pencil-ui-design-system-uview
Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.
Best use case
pencil-ui-design-system-uview is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.
Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "pencil-ui-design-system-uview" skill to help with this workflow task. Context: Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pencil-ui-design-system-uview/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pencil-ui-design-system-uview Compares
| Feature / Agent | pencil-ui-design-system-uview | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# uView Design System Initializer
**Constraint**: Only use this skill when the user explicitly mentions "Pencil" and "uView" (2.x, not uView Pro) or when orchestrating a Pencil design system initialization task.
## When to use this skill
Use this skill when:
- The user wants to initialize uView 2.x tokens (primary, success, warning, error colors) in a Pencil .pen file
- The user needs a component overview frame for uView 2.x components in Pencil
- The user mentions "Pencil" together with "uView" (2.x, not Pro) or uView-specific components (Button, Cell, Tabs, Navbar)
- An orchestrator skill (pencil-ui-designer) routes a uView 2.x initialization request
## How to use this skill
This skill outputs a PENCIL_PLAN. The Agent then calls Pencil MCP tools in order: `open_document`, `set_variables`, `batch_design`, optionally `get_screenshot`.
### Step 1: Initialize Variables (set_variables)
Use `mcp__pencil__set_variables` to register uView 2.x design tokens. Follow .pen file schema.
**Primary / Semantic**
- `u-type-primary`: `#3c9cff`
- `u-type-success`: `#5ac725`
- `u-type-warning`: `#f9ae3d`
- `u-type-error`: `#f56c6c`
- `u-type-info`: `#909399`
**Text & Border**
- `u-main-color`: `#303133`
- `u-content-color`: `#606266`
- `u-tips-color`: `#909399`
- `u-border-color`: `#e4e7ed`
- `u-radius`: `4px`
**Font**
- `u-font-size-base`: `14px` (28rpx)
Fill from uView 2.x docs if more tokens are needed.
### Step 2: Create Component Overview Structure (batch_design)
Use `mcp__pencil__batch_design` to create a "Components Overview" frame with sections based on uView 2.x documentation:
1. **Basic (基础)**
- Icon, Button, Layout, Cell, Badge, Tag
2. **Form (表单)**
- Form, Input, Textarea, Radio, Checkbox, Switch, Rate, Upload, Picker, Select, DatetimePicker, Search, NumberBox, CodeInput
3. **Data (数据)**
- Table, List, Calendar, CountDown, CountTo, Progress, CircleProgress
4. **Feedback (反馈)**
- ActionSheet, Modal, Toast, Notify, SwipeAction, Collapse, Popup
5. **Layout (布局)**
- Grid, Divider, Sticky, IndexList, Swiper, Waterfall
6. **Navigation (导航)**
- Navbar, Tabbar, Tabs, BackTop, Link, Section
Organize frames using Auto Layout. Keep each `batch_design` call to maximum 25 operations.
### Example: Initialize uView 2.x Variables
```json
{
"name": "set_variables",
"arguments": {
"filePath": "designs/app.pen",
"replace": false,
"variables": {
"u-type-primary": "#3c9cff",
"u-type-success": "#5ac725",
"u-type-warning": "#f9ae3d",
"u-type-error": "#f56c6c",
"u-main-color": "#303133",
"u-border-color": "#e4e7ed",
"u-font-size-base": "14px"
}
}
}
```
## Best Practices
- Verify token values against uView 2.x documentation (distinct from uView Pro).
- Use `set_variables` with `replace: false` unless a full reset is requested.
- Use Auto Layout for component overview frames.
- Keep each `batch_design` call to maximum 25 operations; split by category if needed.
## Keywords
pencil, uview, uview 2, design system, init, variables, components
## References
- `references/contract.md` – Design tokens and component naming.
- `references/official.md` – Link to official documentation.
- `references/examples.md` – Example PENCIL_PLAN.
- `references/components.md` – Component specifications.Related Skills
uview-pro-vue3
Builds Vue 3 mobile UIs in uni-app using the uView Pro component library (100+ components). Covers Button, Form, List, Modal, Tabs, NavBar, plus built-in HTTP, storage, router, and validator utilities. Use when the user needs to create uni-app interfaces with uView Pro, configure themes, or use uView Pro utility tools.
uniappx-uview-pro
Integrates uView Pro component library into UniAppX (uni-app-x) projects with TypeScript and Composition API, including easycom configuration, pages.json and manifest.json setup, and platform-specific handling. Use when the user needs to add uView Pro components to a UniAppX project, configure TypeScript .uts integration, or handle cross-platform styling.
uniapp-uview
Integrates uView UI component library into UniApp projects including easycom configuration, pages.json and manifest.json setup, SCSS theming, and platform-specific handling (H5, mini-program, App, nvue). Use when the user needs to add uView UI components to a UniApp project, configure easycom auto-import, or handle cross-platform styling.
course-designer
Design structured courses including syllabi, learning objectives using Bloom's taxonomy, lesson plans, and assessment rubrics. Use when the user asks about course design, needs to create a curriculum, write learning objectives, structure educational modules, or build assessment plans.
tauri-app-system-tray
Create and manage system tray icons with menus and click handlers in Tauri v2, handling platform differences. Use when adding a tray icon, building tray menus, toggling window visibility from the tray, or handling macOS/Windows/Linux tray conventions.
tauri-app-file-system
Read and write local files using the Tauri v2 file-system plugin with scoped directory access. Use when implementing file read/write operations, configuring safe directory scopes, or building import/export file workflows.
stitch-uviewpro-components
Convert Stitch designs into uni-app + Vue 3 + uView Pro pages and components. Use when the user mentions uView Pro, uviewpro, or uni-app Vue 3 conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to rpx/theme, enforces u-* component contracts (u-tabs, u-form, u-picker, u-card) with script setup.
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).
stitch-ui-designer
Master orchestrator for end-to-end Stitch UI design and generation. Use when the user asks to design, create, or make a UI screen using Stitch. Coordinates design spec generation, framework contract injection, prompt assembly, and MCP execution (create_project, generate_screen_from_text, get_screen) in a single workflow.
stitch-ui-design-variants
Generate alternative Stitch design variant prompts for A/B testing and creative exploration. Use when the user wants multiple style, layout, or content options for a Stitch screen. Takes a base Design Spec or prompt and produces 3 distinct variants (layout, style, or content variations).
stitch-ui-design-spec-vant
Vant 4 (Vue 3/Mobile) design spec for Stitch screen generation. Use when the user mentions Vant, vant4, or vant-ui in a Stitch design request. Outputs a hard-constraints prefix with Vant tokens (Primary #1989fa, van-button/van-field/van-nav-bar components, mobile-first 375px) or a CONTRACT_SELECTION_JSON_V1 selector.
stitch-ui-design-spec-uviewpro
uView Pro (uni-app/Vue 3) design spec for Stitch screen generation. Use when the user mentions uview-pro, uviewpro, or uview 3.0 in a Stitch design request. Outputs a hard-constraints prefix with uView Pro tokens (Primary #3c9cff, rpx units, u-button/u-form/u-navbar components, script setup) or a CONTRACT_SELECTION_JSON_V1 selector.