Naming Convention

SkillMedia

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

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Naming Convention skill

What this skill tells your AI

The instructions your AI receives, as published by infrasity-labs/dev-gtm-claude-skills in .claude/skills/naming-convention/SKILL.md and read by ahel’s review.

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

Signals

GitHub stars
124
Forks
11
Last commit
Jun 2026
Advanced
Catalog kind
skill
Gateway key
naming-convention
Source
github.com/infrasity-labs/dev-gtm-claude-skills