npx skills add https://github.com/owl-listener/designer-skills
infrasity-labs/dev-gtm-claude-skills
naming-convention
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
Installation
npx skills add infrasity-labs/dev-gtm-claude-skills --skill naming-convention
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Establish naming rules for components, tokens, and layers with patterns and worked examples. Us…
1.5K installsGuidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsAlso in this package
Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.
npx skills add infrasity-labs/dev-gtm-claude-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,148 B -
docs
SUMMARY.md136 B
History
- First seen on skills.sh
- First recorded snapshot · 54 installs
SKILL.md
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