pencil-design（铅笔设计）

Pencil Design

Expert design assistant for.pen files via Pencil MCP tools. Handles the full workflow: ideation, style guide, component reuse, section-by-section building, visual verification, and design-to-code export.

Prerequisites

• Pencil Desktop App or VS Code/Cursor extension must be running BEFORE Claude Code starts
• MCP tools are deferred — load via ToolSearch(query: "+pencil") before first use
• .pen files are JSON-based, Git-friendly, no auto-save (remind user: Cmd+S)

Agent Delegation

This skill runs in main context — MCP tool calls require ToolSearch which only main context and general-purpose agents have. For large multi-screen designs, delegate individual screens to general-purpose sub-agents with explicit instructions.

Design Workflow

Standard 10-Step Flow

1. ToolSearch("+pencil")           ← Load MCP tools (once per session)
2. get_editor_state                ← Current file, selection, context
3. batch_get(reusable: true)       ← Discover existing components
4. get_variables                   ← Read design tokens
5. get_guidelines(topic)           ← Load rules for task type
6. get_style_guide_tags            ← Browse style options (optional)
   get_style_guide(tags)           ← Get visual direction (optional)
7. find_empty_space_on_canvas      ← Find placement space
8. batch_design                    ← Build section by section
9. get_screenshot                  ← Visual verify EACH section
10. snapshot_layout(problemsOnly)  ← Detect overlaps/clipping

Repeat steps 8-10 for each section. Never build an entire page in one batch_design call.

Topic Selection for get_guidelines

Load multiple topics when relevant (e.g., web-app + design-system).

batch_design Operations

Seven operations, max 25 per call. Operations execute sequentially; any failure rolls back all.

Binding Rules

• Every I/C/R must have a binding name: myCard=I(...) not just I(...)
• document is the predefined root binding
• Bindings are valid only within a single batch_design call
• Use + for path navigation: U(card+"/titleText", {content: "New"})

Copy Gotcha

Copy gives all descendants new IDs. Do NOT U() on copied children — use the descendants parameter in the Copy call itself to modify children during copy.

Critical Rules

1. Reuse components — Always batch_get(reusable: true) first, insert via ref
2. Use variables — Reference token names, not hex values
3. Prevent text overflow — Set wrap, constrain width, use fill_container
4. Verify every section — get_screenshot + snapshot_layout(problemsOnly: true)
5. No image node type — Images are fills on frame/rectangle via G()
6. Semantic naming — UserAvatarImage not Frame 42
7. 25 ops max per batch_design — split larger builds across calls
8. Section-by-section — Build iteratively: plan → build → verify → fix → next

Design-to-Code Export

1. get_guidelines("code") + get_guidelines("tailwind")
2. get_variables → map tokens to Tailwind @theme directives
3. batch_get → read full design tree
4. Map Pencil components → shadcn/ui (or target library)
5. Generate semantic classes: bg-primary not bg-[#3b82f6]
6. Use CVA for variants, cn() for class merging, Lucide for icons

Style Systems

4 built-in design systems: Shadcn UI, Halo, Lunaris, Nitro. Select one early — reduces token cost by referencing known patterns.

Quick Reference

Keyboard Shortcuts

Figma Import

Ctrl+C in Figma → Ctrl+V in Pencil. Images don't transfer (re-add manually). Complex designs: paste in sections to avoid clipboard limits.

CLI (Desktop App Only)

pencil --agent-config config.json

Config is a JSON array — each entry opens a separate Pencil window running its own agent:

[
  {"file": "./screen1.pen", "prompt": "Design a dashboard", "model": "claude-4.5-sonnet"},
  {"file": "./screen2.pen", "prompt": "Design a login page", "model": "claude-4.5-haiku"},
  {"file": "./screen3.pen", "prompt": "Design settings", "model": "claude-4.5-haiku"}
]

Multi-agent parallel design:

• Each entry = independent window + independent Claude API call
• No documented concurrency limit (tested up to 6)
• .pen files must be pre-created (CLI cannot create new files)
• Use haiku for simple screens, sonnet/opus for complex ones
• Bottleneck: RAM per window + API rate limit, not Pencil itself
• Headless CLI (no GUI) coming soon — better for large-scale parallel runs

Pre-create empty files: for i in {1..6}; do echo '{}' > "screen${i}.pen"; done

Token Optimization

• Select a design system upfront (AI references known patterns)
• Hide/delete irrelevant canvas frames before starting
• Use low readDepth / searchDepth values in batch_get
• Build section by section, not entire page at once

Integration

• frontend-design — Load for unique visual identity (avoid generic AI aesthetic)
• brand-guidelines — Apply brand tokens to.pen designs
• canvas-design — Different tool: PNG/PDF art, not.pen files

Additional Resources

Reference Files

• references/batch-design-examples.md — Common batch_design patterns and recipes
• references/troubleshooting.md — Known issues, gotchas, and workarounds