Layui Design System Initializer

Constraint: Only use this skill when the user explicitly mentions "Pencil" and "Layui" (or "layui-vue") 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 Layui 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 PENCILPLAN. The Agent then calls Pencil MCP tools in order: opendocument, setvariables, batchdesign, optionally get_screenshot.

Step 1: Initialize Variables (set_variables)

Use mcppencilset_variables to register Layui design tokens. Follow .pen file schema.

Primary / Theme

• layui-primary: #1e9fff (Layui default blue)
• layui-normal: #1e9fff
• layui-warm: #ffb800
• layui-danger: #ff5722

Text & Border

• layui-text: #333333
• layui-border: #e6e6e6

Font & Radius

• layui-font-md: 14px
• layui-radius: 2px (Layui default)

Fill from official Layui docs if more tokens are needed.

Step 2: Create Component Overview Structure (batch_design)

Use mcppencilbatch_design to create a "Components Overview" frame with sections based on Layui documentation:

1. Basic (基础)

- Button, Form, Input, Textarea, Select, Checkbox, Radio, Switch

1. Layout (布局)

- Container, Grid, Card

1. Data (数据)

- Table, Tree, Pagination, Badge, Tag

1. Feedback (反馈)

- Alert, Message, Modal, Drawer, Loading

1. Navigation (导航)

- Menu, Tabs, Breadcrumb, Dropdown

1. Other (其他)

- Icon, Divider, Timeline

Organize frames using Auto Layout. Keep each batch_design call to maximum 25 operations.

Best Practices

• Verify token values against Layui official documentation.
• Use set_variables with replace: false unless a full reset is requested.
• Use Auto Layout for component overview frames.

Keywords

pencil, layui, layui-vue, 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)

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