Goal: Generate creative, memorable product names that reflect brand identity, market positioning, and are domain-available.Documentation Index
Fetch the complete documentation index at: https://docs.getcore.me/llms.txt
Use this file to discover all available pages before exploring further.
Tools Required
This skill runs using CORE memory only. No integrations required.Step 1: Understand Naming Context
Clarify the naming scope:- What are we naming? New product, feature, company, or sub-brand?
- Core value prop: What’s the product’s main benefit?
- Target audience: Who’s using it? What language resonates?
- Market positioning: Premium, playful, serious, innovative?
- Brand fit: Standalone brand or sub-brand of existing company?
- Geographic scope: English-only, international, multilingual?
Step 2: Define Naming Principles
Set constraints and criteria:- Length: Single word, two words, or phrase? (shorter = better recall)
- Pronunciation: Must be easy to spell and say
- Meaning alignment: Should it literally mean something, or be invented?
- Tone: Professional, playful, technical, aspirational?
- Differentiation: Must feel fresh vs. category terms
- Domain availability: Must be available as .com or primary TLD?
Step 3: Brainstorm Naming Strategies
Generate names using these approaches: Strategy 1: Descriptive / Literal- Directly name the benefit or tool
- Examples: Dropbox, Evernote, Slack
- Pros: Clear meaning, easy to understand
- Cons: Might feel generic or uninspired
- Use an analogy or concept that reflects value
- Examples: Zoom, Figma, Notion
- Pros: Memorable, evocative
- Cons: Meaning might be unclear initially
- Use founder name or character
- Examples: Gmail, Stripe
- Pros: Personal, build founder brand
- Cons: Limits brand growth beyond founder
- Combine two meaningful words
- Examples: Instagram, Pinterest, Slack
- Pros: Descriptive yet fresh
- Cons: Might be taken or hard to trademark
- Create a new word (mashup or neologism)
- Examples: Uber, Airbnb, Spotify
- Pros: Completely unique, memorable
- Cons: Requires brand investment to define meaning
- Use initials or shortened form
- Examples: IBM, IKEA, H&M
- Pros: Short, catchy
- Cons: Loses meaning unless well-established
- Named after place, tradition, or cultural concept
- Examples: Django, Kubernetes
- Pros: Distinctive, story-rich
- Cons: May not be globally relevant
Step 4: Generate Name Candidates
Create 10-15 candidate names across strategies: For each candidate, note:- Strategy used
- Meaning/reasoning
- Tone fit
- Potential domain availability (yes/maybe/no)
- Trademark difficulty (easy/medium/hard)
Step 5: Evaluate Against Criteria
Score each name on:- Clarity: Does target audience understand what it is?
- Memorability: Is it easy to remember and repeat?
- Differentiation: Does it stand out from competitors?
- Brand fit: Does it feel right for the product?
- Pronunciation: Is it easy to spell and say?
- Domain viability: Can we secure the domain?
- Trademark risk: Can we trademark it?
- Global appropriateness: Any negative meanings in other languages?
Step 6: Validate with Target Audience
For top candidates:- Share names with 5-10 target customers or advisors
- Ask: “What does this name make you think of?”
- Listen for: Clarity, positive associations, memorability
- Note any concerns or confusions
- Pick strongest based on feedback
Step 7: Check Legal & Technical Viability
For final choice:- Domain check: Is .com available? Alternatives?
- Social handles: Available on Twitter, LinkedIn, etc.?
- Trademark search: Any conflicts in relevant classes?
- Global check: Negative meanings in key markets?
- URL/email: Easy to type, remember?
Output Format
Product Name Brainstorm — [Product / Feature Name] Naming Context
- Product/scope: [What are we naming?]
- Core benefit: [Main value in one sentence]
- Target audience: [Who will use this?]
- Brand tone: [Professional / Playful / Technical / Aspirational]
- Domain requirement: [.com required? International scope?]
- Length: [Single word / Two words / Phrase]
- Meaning: [Literal / Metaphorical / Invented]
- Pronunciation: [Must be easy to spell and say]
- Differentiation: [Must feel fresh vs. category]
| Name | Strategy | Meaning | Tone fit | Domain | Trademark | Score |
|---|---|---|---|---|---|---|
| [Name 1] | Descriptive | [What it means] | Strong / OK / Weak | Available / Maybe / No | Easy / Med / Hard | [8/10] |
| [Name 2] | Metaphorical | [What it means] | Strong / OK / Weak | Available / Maybe / No | Easy / Med / Hard | [8/10] |
| [Name 3] | Invented | [What it means] | Strong / OK / Weak | Available / Maybe / No | Easy / Med / Hard | [7/10] |
- Strategy: [Strategy type]
- Meaning: [What it conveys]
- Why it works: [Strengths]
- Concerns: [Potential issues]
- Validation feedback: [What people said when shown this name]
- Strategy: [Strategy type]
- Meaning: [What it conveys]
- Why it works: [Strengths]
- Concerns: [Potential issues]
- Validation feedback: [What people said when shown this name]
- Domain: [.com available?]
- Social handles: [Available on key platforms?]
- Trademark: [Searchable? Any conflicts?]
- Global check: [Any negative meanings?]
- Competitive: [Any similar names in market?]
Edge Cases
- Domain not available: Consider alternative TLDs (.co, .io, .app, .dev). Or slightly modify the name. Test new variant with audience first.
- Trademark conflicts: Work with legal to assess conflict severity. May need to modify name, license from trademark holder, or pursue cancellation.
- Name means different thing in key market: Test with native speakers in that market. If negative association is strong, pick different name. If neutral, proceed with explanation/branding.
- Team can’t decide between finalists: Run A/B test with customers or hold vote weighted by decision criteria (trademark risk, domain, clarity). Or pick the one that tests strongest with target audience.
- Audience feedback is split: Some like name A, others like name B. Choose based on alignment with business strategy, scalability, or test with larger audience segment.
