Element Plus Design System Initializer
Constraint: Only use this skill when the user explicitly mentions "Pencil" and "Element" (or "Element Plus") or when orchestrating a Pencil design system initialization task.
When to use this skill
Use this skill when you need to initialize a new design system based on Element Plus specifications, specifically to set up the global color palette and create the initial component library frames in a .pen file.
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 Element Plus design tokens. Follow .pen file schema.
Primary / Semantic
el-color-primary: #409eff
el-color-success: #67c23a
el-color-warning: #e6a23c
el-color-danger: #f56c6c
el-color-info: #909399
Text & Border
el-text-color-primary: #303133
el-text-color-regular: #606266
el-text-color-secondary: #909399
el-border-color: #dcdfe6
el-border-radius-base: 4px
Font
Fill from Element Plus theme 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 Element Plus documentation:
- Basic (基础)
- Layout (布局)
- Form (表单)
- Radio, Checkbox, Input, InputNumber, Select, Cascader, Switch, Slider, TimePicker, DatePicker, DateTimePicker, Form, Upload, Rate
- Data (数据)
- Table, Tag, Progress, Tree, Pagination, Avatar, Skeleton, Empty
- Navigation (导航)
- Menu, Tabs, Breadcrumb, PageHeader, Dropdown, Steps
- Feedback (反馈)
- Alert, Loading, Message, MessageBox, Notification, Dialog, Drawer, Popover, Tooltip
Organize frames using Auto Layout. Keep each batch_design call to maximum 25 operations.
Best Practices
- Verify token values against Element Plus theme documentation.
- Use
set_variables with replace: false unless a full reset is requested.
- Use Auto Layout for component overview frames.
Keywords
pencil, element, element plus, 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.
能力边界
✅ 适用场景
- 当你需要使用此技能对应的技术栈时
- 当项目需要遵循最佳实践时
- 当需要快速上手或深入理解核心概念时
⚠️ 需要注意
- 复杂业务逻辑需要结合具体场景调整
- 性能优化需要根据实际数据量评估
❌ 不适用场景
常见陷阱 (Gotchas)
- 版本兼容性:注意框架版本与依赖库的兼容性,不同版本 API 可能有差异
- 配置文件格式:配置文件格式错误是最常见的问题,建议使用编辑器的语法检查
- 环境变量:确保所有必要的环境变量已正确设置,敏感信息不要硬编码
- 依赖冲突:多版本共存时注意依赖冲突,使用 lock 文件锁定版本
- 性能陷阱:大数据量场景下注意性能优化,避免 N+1 查询等常见问题
1---2name: pencil-ui-design-system-element3description: Initialize Element Plus. design system components in Pencil variables and component overview.4license: Complete terms in LICENSE.txt5---678# Element Plus Design System Initializer910**Constraint**: Only use this skill when the user explicitly mentions "Pencil" and "Element" (or "Element Plus") or when orchestrating a Pencil design system initialization task.1112## When to use this skill1314Use this skill when you need to initialize a new design system based on Element Plus specifications, specifically to set up the global color palette and create the initial component library frames in a .pen file.1516## How to use this skill1718This skill outputs a PENCIL_PLAN. The Agent then calls Pencil MCP tools in order: `open_document`, `set_variables`, `batch_design`, optionally `get_screenshot`.1920### Step 1: Initialize Variables (set_variables)2122Use `mcp__pencil__set_variables` to register Element Plus design tokens. Follow .pen file schema.2324**Primary / Semantic**25- `el-color-primary`: `#409eff`26- `el-color-success`: `#67c23a`27- `el-color-warning`: `#e6a23c`28- `el-color-danger`: `#f56c6c`29- `el-color-info`: `#909399`3031**Text & Border**32- `el-text-color-primary`: `#303133`33- `el-text-color-regular`: `#606266`34- `el-text-color-secondary`: `#909399`35- `el-border-color`: `#dcdfe6`36- `el-border-radius-base`: `4px`3738**Font**39- `el-font-size-base`: `14px`4041Fill from Element Plus theme docs if more tokens are needed.4243### Step 2: Create Component Overview Structure (batch_design)4445Use `mcp__pencil__batch_design` to create a "Components Overview" frame with sections based on Element Plus documentation:46471. **Basic (基础)**48 - Button, Link, Icon492. **Layout (布局)**50 - Container, Grid, Divider513. **Form (表单)**52 - Radio, Checkbox, Input, InputNumber, Select, Cascader, Switch, Slider, TimePicker, DatePicker, DateTimePicker, Form, Upload, Rate534. **Data (数据)**54 - Table, Tag, Progress, Tree, Pagination, Avatar, Skeleton, Empty555. **Navigation (导航)**56 - Menu, Tabs, Breadcrumb, PageHeader, Dropdown, Steps576. **Feedback (反馈)**58 - Alert, Loading, Message, MessageBox, Notification, Dialog, Drawer, Popover, Tooltip5960Organize frames using Auto Layout. Keep each `batch_design` call to maximum 25 operations.6162## Best Practices6364- Verify token values against Element Plus theme documentation.65- Use `set_variables` with `replace: false` unless a full reset is requested.66- Use Auto Layout for component overview frames.6768## Keywords6970pencil, element, element plus, design system, init, variables, components7172## References7374- `references/contract.md` – Design tokens and component naming.75- `references/official.md` – Link to official documentation.76- `references/examples.md` – Example PENCIL_PLAN.77- `references/components.md` – Component specifications.7879## 能力边界8081### ✅ 适用场景82- 当你需要使用此技能对应的技术栈时83- 当项目需要遵循最佳实践时84- 当需要快速上手或深入理解核心概念时8586### ⚠️ 需要注意87- 复杂业务逻辑需要结合具体场景调整88- 性能优化需要根据实际数据量评估8990### ❌ 不适用场景91- 不相关的技术栈或框架92- 需要完全自定义的特殊场景9394## 常见陷阱 (Gotchas)95961. **版本兼容性**:注意框架版本与依赖库的兼容性,不同版本 API 可能有差异972. **配置文件格式**:配置文件格式错误是最常见的问题,建议使用编辑器的语法检查983. **环境变量**:确保所有必要的环境变量已正确设置,敏感信息不要硬编码994. **依赖冲突**:多版本共存时注意依赖冲突,使用 lock 文件锁定版本1005. **性能陷阱**:大数据量场景下注意性能优化,避免 N+1 查询等常见问题