Product Naming Skill
A name has to do a lot of work: signal what the thing is, fit the brand, be easy to say and remember, and not
already be taken. This skill generates candidates across different naming strategies and then evaluates them
against criteria — so you get a defensible shortlist and a recommendation, not a brainstorm dump.
Working from a brief
Given "name our new analytics feature", produce names anyway — infer the audience, the brand feel, and what
the name must convey, and label assumptions. Always flag that trademark, domain, and existing-use checks are
required before adopting any name — propose, don't certify availability.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- What it is — the product/feature, what it does, and the value it delivers.
- Audience & brand — who it's for, the existing brand/name family, and the desired feel (serious, playful, technical, premium).
- Constraints — must convey X, avoid Y, language/market considerations, length.
- Context — is it a standalone brand, a sub-brand, or a feature within an existing product (descriptive often wins for features).
Output Format
Naming: [thing]
1. Direction — a line on what the name should achieve and the strategy mix that fits.
2. Candidates by strategy — a shortlist grouped by approach, each with a one-line rationale:
| Strategy |
Examples |
Feel |
| Descriptive |
(says what it does) |
clear, SEO-friendly, lower distinctiveness |
| Evocative / metaphor |
(suggests a quality) |
memorable, needs context |
| Invented / coined |
(new word) |
ownable, needs building |
| Compound / blend |
(two ideas joined) |
balance of clarity + distinctiveness |
3. Evaluation — score the top candidates against criteria:
| Name |
Clear |
On-brand |
Memorable |
Easy to say/spell |
Extensible |
Notes |
4. Recommendation — the top pick (or 2), why, and the checks to run before committing: trademark search, domain/handle availability, existing-product collision, and meaning in target languages.
Quality Checks
Anti-Patterns
Based On
Brand & product naming practice — strategy-driven generation, criteria-based evaluation, and pre-adoption availability/meaning checks.
Example Trigger Phrases
- "Name this product."
- "Brainstorm names for our feature."
- "Choose between these name candidates."
- "Name our company."
1---2name: product-naming3description: "Generate and evaluate names for a product, feature, or release. Use when asked to name a product/feature/company, brainstorm naming options, or choose between name candidates. Produces a shortlist of names across naming strategies, each with rationale, plus an evaluation against clear criteria (clarity, fit, memorability, availability checks to run) and a recommendation — not just a random list."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/product-naming7---89# Product Naming Skill1011A name has to do a lot of work: signal what the thing is, fit the brand, be easy to say and remember, and not12already be taken. This skill generates candidates across different naming strategies and then *evaluates* them13against criteria — so you get a defensible shortlist and a recommendation, not a brainstorm dump.1415## Working from a brief1617Given "name our new analytics feature", **produce names anyway** — infer the audience, the brand feel, and what18the name must convey, and label assumptions. Always flag that **trademark, domain, and existing-use checks are19required before adopting** any name — propose, don't certify availability.2021## Required Inputs2223Ask for these only if they aren't already provided (else infer and label):2425- **What it is** — the product/feature, what it does, and the value it delivers.26- **Audience & brand** — who it's for, the existing brand/name family, and the desired feel (serious, playful, technical, premium).27- **Constraints** — must convey X, avoid Y, language/market considerations, length.28- **Context** — is it a standalone brand, a sub-brand, or a feature within an existing product (descriptive often wins for features).2930## Output Format3132### Naming: [thing]3334**1. Direction** — a line on what the name should achieve and the strategy mix that fits.3536**2. Candidates by strategy** — a shortlist grouped by approach, each with a one-line rationale:3738| Strategy | Examples | Feel |39|---|---|---|40| Descriptive | (says what it does) | clear, SEO-friendly, lower distinctiveness |41| Evocative / metaphor | (suggests a quality) | memorable, needs context |42| Invented / coined | (new word) | ownable, needs building |43| Compound / blend | (two ideas joined) | balance of clarity + distinctiveness |4445**3. Evaluation** — score the top candidates against criteria:4647| Name | Clear | On-brand | Memorable | Easy to say/spell | Extensible | Notes |48|---|---|---|---|---|---|---|4950**4. Recommendation** — the top pick (or 2), why, and the **checks to run before committing**: trademark search, domain/handle availability, existing-product collision, and meaning in target languages.5152## Quality Checks5354- [ ] Names span more than one strategy (not all coined, not all descriptive)55- [ ] Each candidate has a rationale tied to what the name must convey56- [ ] Top names are scored against explicit criteria, not vibes57- [ ] For a *feature* within a product, descriptive/clear options are prioritised over clever ones58- [ ] A recommendation is made, with required availability checks listed59- [ ] Language/market pitfalls are flagged for the shortlist6061## Anti-Patterns6263- [ ] Do not hand back a flat list with no evaluation or recommendation64- [ ] Do not claim a name is "available" — you can't verify trademarks/domains; list the checks to run65- [ ] Do not over-index on clever/coined names for features that just need to be findable66- [ ] Do not ignore pronounceability/spelling — a name people can't say or type costs you word-of-mouth67- [ ] Do not skip cross-language/meaning checks for names going to multiple markets6869## Based On7071Brand & product naming practice — strategy-driven generation, criteria-based evaluation, and pre-adoption availability/meaning checks.7273## Example Trigger Phrases7475- "Name this product."76- "Brainstorm names for our feature."77- "Choose between these name candidates."78- "Name our company."