penpot-component-factory

Automate Penpot component creation with variant matrices and tokenized design systems.

33|3|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/penpot/penpot-ai-kit --skill penpot-component-factory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: penpot-component-factory
Source: https://github.com/penpot/penpot-ai-kit/tree/main/skills/penpot-component-factory
Command: npx skills add https://github.com/penpot/penpot-ai-kit --skill penpot-component-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires shared/penpot-mcp-tool-reference.md, shared/plugin-api-gotchas.md, shared/tokens-schema.json, shared/naming-conventions.md, shared/state-management.md, shared/modes-and-policies.md, shared/visual-self-review.md, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and maintenance of Penpot components, ensuring full variant matrices and tokenized design systems.

Core Features & Use Cases

  • Component Creation: Build complete variant matrices for interactive components with all states and sizes.
  • Variant Management: Add, remove, and manage variants within a component.
  • Tokenization: Ensure all design values are tokenized for consistent theming and governance.
  • Use Case: Use this Skill to create a button component with all its states and sizes, ensuring it's fully tokenized and correctly named.

Quick Start

Create a new button component with variants by running the penpot-component-factory skill and providing the necessary design system and token information.

Frequently Asked Questions about penpot-component-factory

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

FAQPage Schema
How do I automate component creation in Penpot with full variant matrices?

To automate component creation in Penpot, use the component factory to build complete variant matrices for interactive components, handling all states and sizes. It requires the Penpot MCP tool and design system resources to ensure consistent tokenization and naming conventions.

What is tokenization in a Penpot design system and when do I need it?

Tokenization in a Penpot design system ensures all design values are converted to tokens for consistent theming and governance. You need it when building interactive components to maintain visual consistency across all states and sizes.

How do I manage and update variants within an existing Penpot component?

To manage variants within a Penpot component, apply automated variant management to add, remove, or update specific states and sizes. This ensures the full variant matrix remains synchronized with your tokenized design system.

Does the Penpot MCP tool support tokenized design systems for component engineering?

Yes, the Penpot MCP tool supports tokenized design systems for component engineering. It integrates with shared tokens schema and naming conventions to apply design values automatically during component creation and variant management.

What's the best way to ensure consistent naming conventions across Penpot components?

The best way to ensure consistent naming conventions is to automate component creation using a shared naming conventions schema. This guarantees that all variants, states, and tokenized values follow standardized design system governance rules.

Why does my Penpot component variant matrix break when adding new states?

Variant matrices break when added states lack proper tokenization or naming conventions. Use the component factory to apply the shared state management and tokens schema, ensuring new variants integrate correctly without disrupting existing design system structures.