penpot-rename-layers

Rename Penpot layers to semantic HTML element or kebab-case role names.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining clean, semantically meaningful layer names in Penpot files, which is essential for accessibility, code review, and handoff processes.

Core Features & Use Cases

  • Semantic Renaming: Automatically rename Penpot layers to semantic HTML element names or kebab-case role names.
  • Layer Inventory: Builds a comprehensive inventory of all layers, classifying them as auto-generated, semantic, or custom.
  • Batch Renaming: Performs renaming in small, validated batches to avoid errors and ensure accuracy.
  • Use Case: A designer working on a Penpot file can use this Skill to quickly rename all auto-generated layer names to standard semantic names, preparing the file for code generation or accessibility checks.

Quick Start

Use the penpot-rename-layers skill to rename all auto-generated layer names to semantic names in the current Penpot file.

Frequently Asked Questions about penpot-rename-layers

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

FAQPage Schema
How do I automatically rename Penpot layers to semantic HTML element names?

You can automatically rename Penpot layers to semantic HTML element names or kebab-case role names by applying predefined renaming rules to your design file. The skill classifies layers and updates auto-generated names to semantic ones in small validated batches.

Why does my design file need semantic layer naming for accessibility checks?

Semantic layer naming is needed for accessibility checks because it ensures layer names map to meaningful HTML elements or ARIA roles. This semantic structure is essential for clean code review, accurate code generation, and proper handoff processes.

Can I batch rename auto-generated layer names in Penpot without errors?

Yes, you can batch rename auto-generated layer names without errors by processing them in small, validated batches. The skill builds a comprehensive layer inventory first, classifying names as auto-generated, semantic, or custom, to ensure accuracy during the renaming process.

Does semantic layer renaming in Penpot require access to the MCP?

Yes, semantic layer renaming requires access to the Penpot MCP and specific utility scripts. This connection allows the automated renaming process to interact directly with your Penpot files and apply the predefined naming conventions accurately.

What is the best way to prepare Penpot files for code generation and handoff?

The best way to prepare Penpot files for code generation and handoff is to rename all auto-generated layer names to standard semantic names. This process creates a clean layer inventory with meaningful kebab-case role names, ensuring a smooth developer handoff.

What happens to custom layer names during the semantic renaming process?

During the semantic renaming process, the skill builds a comprehensive inventory and classifies layers as auto-generated, semantic, or custom. It targets auto-generated names for renaming to semantic HTML elements, while identifying existing custom and semantic names.