generate-brand-names

name	generate-brand-names
description	Use when the user asks for premium brand names, startup names, product names, domain-style names, or distinctive alternatives to generic descriptive names for SaaS, AI products, developer tools, apps, and digital services.

Generate Brand Names

Goal

Generate short, distinctive names that feel premium, timeless, and brandable rather than descriptive. Avoid generic AI/startup buzzwords and favor names with credible roots in technical, historical, natural, mythological, linguistic, or scientific domains.

Workflow

1. Identify the product category, audience, emotional tone, and any hard constraints from the user prompt.
2. If critical context is missing, make a minimal assumption and state it briefly before the names. Do not block unless the product itself is unclear.
3. Generate a large private candidate pool before answering. Pull from varied source domains:
   • Geology, minerals, metallurgy, and materials
   • Astronomy, orbital mechanics, navigation, and cartography
   • Physics, optics, mathematics, and systems theory
   • Latin, Greek, Sanskrit, Japanese, Old Norse, and other historical languages
   • Architecture, ancient infrastructure, instruments, and craft traditions
   • Mythology and historical figures only when the reference is subtle and not overused
4. Include multiple name structures in the private pool: real but uncommon words, clipped roots, clean compounds, soft inventions, and transformed source terms.
5. Score each candidate against the quality bar, then discard borderline names before answering. Replace any name that is merely "pretty good."
6. Filter out names that sound generic, trend-chasing, hard to say, hard to spell, too close to existing famous brands, or likely to blend into the SaaS/AI category.
7. Present the strongest names first. Prioritize fewer excellent names over many weak names.

Naming Standards

Prefer names that are:

• 4-10 characters when possible, usually one or two syllables.
• Easy to pronounce aloud after one glance.
• Visually clean in a logo, URL, and app header.
• Abstract enough to support future product expansion.
• Distinctive enough to be searchable.
• Rooted in a meaning that can support a brand story without explaining the product literally.
• Specific in feeling, not specific in description: the name should suggest the category promise without naming the feature.
• Strong enough to survive the "would a serious buyer say this in a boardroom?" test.

Avoid:

• Obvious AI terms: ai, gpt, bot, prompt, agent, neural, gen, cortex, synapse, copilot, llm, smart.
• Generic SaaS suffixes: hub, ify, ly, io, base, stack, flow, works, unless the combination is unusually strong.
• Names that over-describe the feature set.
• Forced misspellings that reduce trust.
• Overused mythological or space names unless transformed into something fresh.
• Familiar startup-name shapes that feel interchangeable: Nexa, Vanta-like, -ly, -iq, -ify, -ara, -ora, -base, -pilot, unless there is a compelling reason.
• Generic luxury words that sound premium but say nothing distinctive about the product.

Private Quality Filters

Before showing any name, silently test it against these filters:

Filter	Passes when	Replace when
Boardroom	A serious buyer can say it without embarrassment	It feels cute, gimmicky, or trend-chasing
Category escape	It does not sound like one of many similar AI/SaaS tools	It could be swapped with a competitor name
Root strength	The origin creates a useful brand story	The meaning is decorative but irrelevant
Mouthfeel	It is smooth to say and easy to spell after hearing once	It needs pronunciation coaching
Memorability	It has a sharp visual or phonetic hook	It is pleasant but forgettable
Expansion	It can grow beyond the first feature	It describes the current workflow too literally

If a requested list has 10 names, privately create at least 25 candidates and only show the top 10. If fewer than half feel excellent, say so and provide a tighter shortlist instead of padding.

Output Format

For each name, include:

• Name: the candidate name.
• Origin: source language, domain, object, or concept.
• Meaning: plain-English meaning or association.
• Why it fits: connect the name to the product's positioning, user, or product promise.
• Brand perception: describe how the name is likely to feel in market.
• Watchouts: mention pronunciation, spelling, trademark/domain uncertainty, cultural sensitivity, or category confusion when relevant.

Use this compact table for larger lists:

Name	Origin / Meaning	Why it fits	Brand perception	Watchouts

Use short sections instead of a table when the user asks for a small, high-consideration shortlist.

Do not present every candidate as equally strong. For larger lists, mark the final 2-4 names as the best picks and explain what makes each one stronger than the near-misses. If a name is included despite a weakness, say why it still clears the bar.

Quality Bar

Do not claim domain, trademark, company-name, or social-handle availability unless you have checked live sources in the current turn. If the user asks for available names, search and verify using current sources before making availability claims.

When a name is inspired by a language or culture, avoid sacred, sensitive, or honorific terms unless the product context justifies them. Prefer neutral concepts such as stone, light, measure, path, vessel, star, bridge, craft, order, signal, boundary, and motion.

End with 2-4 best picks and a concise reason for each when the list has more than eight names. The best picks should feel sharper than the rest on category fit, memorability, pronunciation, and premium perception, not merely be the least flawed options.