What is the naming convention skill?
The naming convention skill is a short SKILL.md in the Owl-Listener designer skills repo, inside the design-systems plugin. It tells an AI coding agent to set naming rules with five principles and patterns for components, tokens, files, design pages, code and assets.
It is a compact skill from the design-systems plugin of the designer skills collection. Its description is to establish naming rules for components, tokens and layers with patterns and worked examples.
Inconsistent names are a quiet cost in any design system. This skill gives the agent one fixed pattern per asset type, so a new component or token is named the way the rest already are.
What changes in your agent's output
- Component names follow a category, name, variant and state pattern.
- Token names follow a category, property, concept, variant and state pattern.
- Code follows kebab-case for CSS, PascalCase for React components and camelCase for props.
- Names describe purpose rather than visual properties, and separators stay consistent.
Who it is for
Best for
- Teams whose Figma layers, CSS classes and token names have drifted apart.
- Developers starting a token system who want a naming pattern first, then the values from design-token.
- Reviewers who want name rules before running a check such as figma-component-audit.
Not for
- Anyone who needs to decide what tokens contain. The description points to design-token for that.
- Teams that already have a documented convention. The skill would add a second rule set.
- People wanting automated name linting, which the skill only recommends and does not provide.
Use it with UiChemy
Name layers and components clearly in your design, then use UiChemy Figma to WordPress to convert the finished design into an editable WordPress page. Click Get Started on uichemy.com.
How to install Naming Convention Skill: Names for Components and Tokens
/plugin marketplace add Owl-Listener/designer-skillsThe skill ships inside the design-systems plugin, so installing it brings the other skills in that plugin too.Add the marketplace
Run the command above in Claude Code. The README says this only registers where the skills live and nothing installs yet.
Install the design-systems plugin
Run /plugin install design-systems@designer-skills, or type /plugin, open the Discover tab and tick design-systems.
Gemini CLI route
The README says each plugin is also a Gemini CLI extension. Clone the repo and copy its .gemini/extensions folder into your project.
Ask for naming rules
Ask the agent to set naming rules for components and tokens, or to rename a messy set of layers to one pattern.
Check that it loaded
Ask the agent to name a disabled secondary button component and a hover border token. Names should follow the category, name, variant and state patterns.
Key features
- Five principlesNames should be predictable, consistent, scalable, scannable and unambiguous.
- Component patternUses category, name, variant and state, written as a slash path.
- Token patternUses category, property, concept, variant and state joined into one token name.
- File patternFiles follow type, name, variant and extension, so assets sort and search cleanly.
- Design file pagesDesign files use numbered, descriptive pages and PascalCase component names.
- Code casingSets kebab-case for CSS, PascalCase for React and camelCase for props.
- Asset namesIcons follow icon, name and size, and illustrations follow illust, scene and variant.
- Pitfall listWarns against abbreviations only the author understands, inconsistent separators and names based on visuals instead of purpose.
- Single reference pageBest practices say to document the rules in one reference page and review names in team critiques.
- Prefixes and lintingRecommends prefixes for sorting and grouping and suggests automating name linting.
Frequently asked questions
What is the naming convention skill?
It is a SKILL.md from the Owl-Listener designer skills repo, in the design-systems plugin. It guides an AI coding agent to set naming rules for components, tokens, files, code and assets with fixed patterns and five principles.
How do I install the naming convention skill?
Run /plugin marketplace add Owl-Listener/designer-skills in Claude Code, then /plugin install design-systems@designer-skills. The README also describes a Gemini CLI extension route that copies the repo's .gemini extensions folder into your project.
What naming patterns does it give?
Components use category, name, variant and state. Tokens use category, property, concept, variant and state. Files use type, name, variant and extension. Assets use icon or illust prefixes with name, size or scene and variant.
Which casing does it recommend for code?
Kebab-case for CSS, PascalCase for React components and camelCase for props. Design files use numbered, descriptive pages with PascalCase component names. These come directly from the patterns list in the skill file.
Does it decide what my tokens contain?
No. Its description says that for what the tokens actually contain you should use design-token. See design-token for tiers and values. This skill only sets how names are built and written.
What naming mistakes does it warn about?
Abbreviations only the author understands, inconsistent separators and names based on visual properties instead of purpose. A name like blue-button ages badly when the brand changes, while a purpose based name does not.
Can I use it with Cursor or Codex?
The README names Claude Code and Gemini CLI as the supported tools. For other agents you could copy the SKILL.md text into that tool's rules, but the repo does not document that route.
What are the limits of this skill?
It is a short rule list with no scripts, so it does not lint names itself, though it recommends automating that. Pair it with design-token-audit to find drift in values and rely on code review for names.


