penpot-build-from-code

Convert JSX/TSX, HTML, Vue/Svelte, and CSS code into Penpot designs with semantic tokens.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires penpot-mcp-tool-reference, plugin-api-gotchas, tokens-schema, naming-conventions, state-management, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of converting existing application code into Penpot designs that are bound to the existing design system, enabling seamless integration and theming.

Core Features & Use Cases

  • Code-to-Design Conversion: Converts JSX/TSX, HTML, Vue/Svelte, CSS/Tailwind, and styled-components code into Penpot screens.
  • Semantic Token Binding: Ensures all styles are bound to semantic tokens for consistency and theming capabilities.
  • Component Reuse: Utilizes library components instead of raw shapes for consistency and maintainability.
  • Use Case: For a developer who wants to convert an existing React application into a Penpot design, this skill can map React components and styles to their Penpot equivalents, maintaining the design system and theming across the platform.

Quick Start

Use the penpot-build-from-code skill to convert your React app's landing page into a Penpot design by providing the JSX code in the input file 'landing-page.js'.

Frequently Asked Questions about penpot-build-from-code

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

FAQPage Schema
How do I convert React code to Penpot designs?

To convert React code to Penpot designs, provide your JSX or TSX code as input. The process maps code styles to semantic tokens and utilizes library components to ensure the resulting Penpot screens match your existing design system.

Can I convert HTML and Vue components into Penpot screens?

Yes, you can convert HTML and Vue components into Penpot screens. The conversion supports various markup languages including Vue/Svelte, CSS/Tailwind, and styled-components, transforming structured UI code into bound Penpot designs.

Does code to design conversion maintain design system tokens?

Yes, code to design conversion maintains design system tokens through semantic token binding. This ensures all converted code styles are bound to semantic tokens, providing consistency and theming capabilities across the generated Penpot screens.

What is the best way to map styled-components to Penpot library components?

The best way to map styled-components to Penpot library components is by utilizing the component reuse feature. Instead of creating raw shapes, the process matches code styles to semantic tokens and replaces them with existing library components for maintainability.

Do I need an existing design system to convert code into Penpot?

Yes, you need an existing design system to convert code into Penpot accurately. The process requires knowledge of your design system for accurate semantic token binding and to ensure codebases with structured UI components map correctly to library components.

Why does my converted code use raw shapes instead of library components in Penpot?

Your converted code uses raw shapes instead of library components when the code lacks structured UI components or the design system knowledge is missing. Accurate component mapping requires applying semantic tokens and utilizing existing library components for consistency.