OpenSkillIndex← back to search
claude-code

Designer-skills naming-convention

Establish a naming convention system for design elements, components, and tokens with clear rules and examples.

install
source · Clone the upstream repo
git clone https://github.com/Owl-Listener/designer-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/Owl-Listener/designer-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/design-systems/skills/naming-convention" ~/.claude/skills/owl-listener-designer-skills-naming-convention && rm -rf "$T"
manifest: design-systems/skills/naming-convention/SKILL.md
source content

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

  1. 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