Naming strategy
Skill Dragoon0x/everything-design-taste/skills/naming-strategy
Product and feature naming, naming conventions, and linguistic considerations.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill naming-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 252 tokens by cl100k_base, as published. Nobody here has run it
Naming Strategy
Product Naming Approaches
| Type | Example | Pros | Cons |
|---|---|---|---|
| Descriptive | Microsoft Teams | Clear function | Generic |
| Invented | Spotify | Unique, ownable | Needs marketing |
| Metaphor | Slack | Memorable | Can confuse |
| Founder | Bloomberg | Personal, trustworthy | Limited scalability |
| Acronym | IBM | Short | Meaningless initially |
Feature Naming Rules
- Descriptive over clever (users need to find it, not enjoy the pun)
- Consistent vocabulary (don't call it 'workspace' in one place and 'project' in another)
- Verb-first for actions ('Create project' not 'Project creation')
- Avoid internal jargon (what engineers call it isn't what users should see)
- Test with users: 'What would you expect this to do?'
Linguistic Testing
- Does it translate well? (no accidental meanings in other languages)
- Is it easy to pronounce? (for word-of-mouth growth)
- Is it searchable? (unique enough to rank in Google)
- Is the domain available? (.com or relevant TLD)
- Is the social handle available?
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.