
Naming Convention
This one helps you set up consistent naming patterns across your design system, from component variants to design tokens to file names. It gives you actual patterns to follow (like kebab-case for CSS, PascalCase for React components) and warns against common mistakes like cryptic abbreviations or inconsistent separators. The real value is having a reference that stops the endless debates about whether to use dashes or underscores, and getting everyone on the team to speak the same language. It won't write your names for you, but it'll give you the framework so your button-primary-disabled actually makes sense six months from now when someone else touches the code.
- skills.sh installs
- 2.3K
- GitHub stars
- 3.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill naming-convention --agent claude-codeInstalls into .claude/skills of the current project.
Files
Naming Convention
You are an expert in creating clear, scalable naming systems for design assets, components, and tokens.
What You Do
You establish naming conventions that make design systems predictable, searchable, and maintainable.
Principles
- Predictable 2. Consistent 3. Scalable 4. Scannable 5. Unambiguous
Patterns
- Components: [category]/[name]/[variant]/[state]
- Tokens: {category}-{property}-{concept}-{variant}-{state}
- Files: [type]-[name]-[variant].[ext]
- Design files: Numbered + descriptive pages, PascalCase components
- Code: kebab-case CSS, PascalCase React, camelCase props
- Assets: icon-[name]-[size], illust-[scene]-[variant]
Common Pitfalls
- Abbreviations only the author understands
- Inconsistent separators
- Names based on visual properties instead of purpose
Best Practices
- Document rules in a single reference page
- Automate name linting
- Use prefixes for sorting and grouping
- Review names in team critiques
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Categories
- Code Review & Quality, Design & UI/UX
- First seen
- Jun 3, 2026
More from owl-listener/designer-skills
All 68- Empathy Map2.3K
- Documentation Template2.3K
- Pattern Library2.3K
- Affinity Diagram2.3K
- Interview Script2.3K
- Card Sort Analysis2.3K
- Design Rationale2.3K
- Accessibility Test Plan2.3K
- A B Test Design2.3K
- Metrics Definition2.3K
- Diary Study Plan2.3K
- Stakeholder Alignment2.3K
- Test Scenario2.3K
- Design Review Process2.3K
- North Star Vision2.3K
- Opportunity Framework2.3K
- Summarize Interview2.2K
- Design System Adoption2.2K
- Team Workflow2.2K
- Design Sprint Plan2.2K
- Click Test Plan2.2K
- Version Control Strategy2.2K
- Information Architecture2.2K
- Aesthetic Usability2.2K