pencil-design

Convert Pencil .pen designs into React/Next.js and Tailwind v4 code.

21|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/chiroro-jr/pencil-design-skill --skill pencil-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pencil-design
Source: https://github.com/chiroro-jr/pencil-design-skill/tree/main
Command: npx skills add https://github.com/chiroro-jr/pencil-design-skill --skill pencil-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables AI agents to design production-quality UIs in Pencil (.pen files) and generate clean, maintainable code from Pencil designs, bridging design and code workflows between design tooling and frontend development.

Core Features & Use Cases

  • Reuse design system components by inserting reusable ref instances to ensure consistency across screens.
  • Enforce design tokens and semantic Tailwind utilities to support theming, consistency, and faster iteration.
  • Generate production-ready React/Next.js + Tailwind v4 + shadcn/ui code from Pencil designs, with visual verification and layout checks.
  • Use Pencil MCP tools to accelerate design-to-code workflows, token syncing, and import/export of design data.

Quick Start

Design a Pencil UI and generate production-ready code from your .pen design.

Frequently Asked Questions about pencil-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate React code from Pencil designs?

You can generate production-ready React and Next.js code from Pencil designs by mapping Pencil variables to Tailwind v4 @theme tokens and reusing design system components to output semantic class names.

Can I sync Pencil design tokens with Tailwind v4 in my codebase?

Yes, syncing Pencil design tokens with your codebase requires mapping Pencil variables directly to Tailwind v4 @theme tokens, ensuring cohesive design systems and consistent theming across UI components.

How do I convert .pen files into shadcn/ui components?

Converting .pen files into shadcn/ui components involves inserting reusable ref instances within Pencil, allowing the generation of maintainable React code with semantic Tailwind utilities and shadcn/ui elements.

What is the best way to maintain design consistency across Pencil UI screens?

The best way to maintain design consistency across Pencil UI screens is by reusing design system components through ref instances and enforcing design tokens via semantic Tailwind utilities during code generation.

Does Pencil design to code generation require Tailwind v4?

Pencil design to code generation targets Tailwind v4 specifically, leveraging the @theme token system to map Pencil variables and ensure the generated React/Next.js code maintains a cohesive design system.

Why are my Pencil design variables not mapping to semantic class names?

Pencil design variables may not map to semantic class names if they are not properly configured as Tailwind v4 @theme tokens or if reusable design system components are not utilized as ref instances.