# Naming Strategy

> Product and feature naming, naming conventions, and linguistic considerations.

- Skill: `dragoon0x/naming-strategy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dragoon0x/naming-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dragoon0x/naming-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dragoon0x (https://skillmd.com/u/dragoon0x)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dragoon0x/naming-strategy

---


# 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
1. Descriptive over clever (users need to find it, not enjoy the pun)
2. Consistent vocabulary (don't call it 'workspace' in one place and 'project' in another)
3. Verb-first for actions ('Create project' not 'Project creation')
4. Avoid internal jargon (what engineers call it isn't what users should see)
5. 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?