agentsclimarketplace

Naming convention

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/naming-convention

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

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill naming-convention

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.1 KB, 237 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.