pencil-ui-design-system-uviewpro
uView Pro Design System Initializer
Constraint: Only use this skill when the user explicitly mentions "Pencil" and "uView Pro" (or "uviewpro") or when orchestrating a Pencil design system initialization task.
When to use this skill
Use this skill when:
- The user wants to initialize uView Pro tokens (primary, error, warning, success colors) in a Pencil .pen file
- The user needs a component overview frame for uView Pro components in Pencil
- The user mentions "Pencil" together with "uView Pro", "uviewpro", or uView Pro-specific components (Button, Form, Tabs, Navbar)
- An orchestrator skill (pencil-ui-designer) routes a uView Pro 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 the following uView Pro design tokens. Follow .pen file schema; variable names are arbitrary strings.
Primary Colors (Blue)
u-type-primary:#2979ffu-type-primary-dark:#2b85e4u-type-primary-disabled:#a0cfffu-type-primary-light:#ecf5ff
Error Colors (Red)
u-type-error:#fa3534u-type-error-dark:#dd6161u-type-error-disabled:#fab6b6u-type-error-light:#fef0f0
Warning Colors (Yellow)
u-type-warning:#ff9900u-type-warning-dark:#f29100u-type-warning-disabled:#fcbd71u-type-warning-light:#fdf6ec
Success Colors (Green)
u-type-success:#19be6bu-type-success-dark:#18b566u-type-success-disabled:#71d5a1u-type-success-light:#dbf1e1
Info Colors (Gray)
u-type-info:#909399u-type-info-dark:#82848au-type-info-disabled:#c8c9ccu-type-info-light:#f4f4f5
Text Colors
u-main-color:#303133(Main Text)u-content-color:#606266(Content Text)u-tips-color:#909399(Tips/Secondary)u-light-color:#c0c4cc(Placeholder)
Background & Border
u-bg-color:#f3f4f6u-border-color:#e4e7ed
Font Sizes (px)
u-font-xs:12px(24rpx)u-font-sm:13px(26rpx)u-font-md:14px(28rpx)u-font-lg:15px(30rpx)u-font-xl:16px(32rpx)
Border Radius
u-radius:4px(8rpx)u-radius-lg:8px(16rpx)u-radius-circle:9999px
Step 2: Create Component Overview Structure (batch_design)
Use mcp__pencil__batch_design to create a "Components Overview" frame containing the following sections (Frames) based on uView Pro documentation:
- Basic Components (基础组件)
- Color, Icon, Image, Button, Layout, Cell, Badge, Tag, Text, Fab, Transition, TodoRootPortal, ConfigProvider
- Form Components (表单组件)
- Form, Input, Textarea, Calendar, Select, Keyboard, Picker, Rate, Search, NumberBox, Upload, VerificationCode, Field, Checkbox, Radio, Switch, Slider
- Data Components (数据组件)
- CircleProgress, LineProgress, Table, CountDown, CountTo
- Feedback Components (反馈组件)
- ActionSheet, AlertTips, Toast, NoticeBar, TopTips, Collapse, Popup, SwipeAction, Modal, FullScreen
- Layout Components (布局组件)
- Line, Card, Mask, NoNetwork, Grid, Swiper, TimeLine, Skeleton, Sticky, Waterfall, Divider
- Navigation Components (导航组件)
- Dropdown, Tabbar, BackTop, Navbar, Tabs, TabsSwiper, Subsection, IndexList, Steps, Empty, Link, Section, Pagination
- Other Components (其他组件)
- MessageInput, Loadmore, TodoReadMore, LazyLoad, Gap, Avatar, Loading, LoadingPopup, safeAreaInset
Organize component frames using Auto Layout. Keep each batch_design call to maximum 25 operations; split by logical sections if needed.
Example: Initialize uView Pro Variables
{
"name": "set_variables",
"arguments": {
"filePath": "designs/app.pen",
"replace": false,
"variables": {
"u-type-primary": "#2979ff",
"u-type-error": "#fa3534",
"u-type-warning": "#ff9900",
"u-type-success": "#19be6b",
"u-main-color": "#303133",
"u-bg-color": "#f3f4f6",
"u-border-color": "#e4e7ed",
"u-font-md": "14px"
}
}
}
Best Practices
- Always verify color values against the latest uView Pro documentation if unsure.
- Use
set_variableswithreplace: falseto merge into existing variables unless a full reset is requested. - Organize component frames using Auto Layout for easy expansion.
- Keep each
batch_designcall to maximum 25 operations; split by category if needed.
Keywords
pencil, uviewpro, uview pro, 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 or usage.references/components.md– Component specifications.
More from partme-ai/full-stack-skills
element-plus-vue3
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
63electron
Build cross-platform desktop applications with Electron, covering main/renderer process architecture, IPC communication, BrowserWindow management, menus, tray icons, packaging, and security best practices. Use when the user asks about Electron, needs to create desktop applications, implement Electron features, or build cross-platform desktop apps.
51uniapp-project
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
40ascii-cli-logo-banner
Entry point for ASCII CLI banners that routes to the Python built-in font skill or figlet.js/FIGfont skill. Use when the user wants a startup banner, ASCII logo, terminal welcome screen, or CLI branding for a service.
38ascii-terminal-animation-pack
Plan and generate terminal ASCII animations/screensaver-style output (FPS, refresh rules, loop policy, low-flicker guidance), with a static poster frame and an optional local demo script.
34ascii-image-to-ascii
“Convert an image into ASCII art (readable + detail variants, width/charset controls, optional ANSI), for terminal previews and plain-text image substitutes.”
34