Domain Name Suggestor
Overview
Use this skill to research brand names and domains for a product, app, or company. Deliver a large, varied shortlist where each finalist is brandable, easy to pronounce, actually registrable at regular retail price, and free of obvious product or business collisions.
Research only. Do not change project code, rename folders, register domains, or commit unless the user explicitly asks.
Workflow
Gather context:
- Product one-liner, audience, market geography, existing brand motifs, liked or rejected names.
- If a project path is provided, audit the product from the codebase or docs first.
- Infer only from observable evidence. Do not invent product claims.
Confirm constraints, then state the defaults you will use:
- Language and naming style
- Primary and secondary TLDs
- Quantity target
- Any hard exclusions from the user
Generate widely across multiple naming styles. Cull weak ideas before availability checks. Choose prefixes, suffixes, metaphors, and constructions yourself based on the product and market. Do not rely on a fixed shortlist of affixes.
Verify domain availability live with registry RDAP first. Prefer the official registry endpoint for the TLD when known; otherwise use a public RDAP bootstrap or lookup service. Treat 200 as taken and 404 as not registered. Fall back to registry WHOIS when RDAP is missing. Never use DNS alone. Never mark a name available from memory. Confirm finalists are regular retail price at a registrar, not premium.
Collision-check serious candidates and all finalists:
- Exact-name web search
- Apps, SaaS products, companies, and famous brands
- Lightweight trademark risk flags
- Crowded exact-name search results
Present results as:
- Top picks with one-line rationale
- Categorized full verified table
- Method notes for how availability was checked
- Optional short near-miss section only if useful
Iterate hard on feedback. If the user rejects a batch, change direction instead of defending weak names. When asked for finals, consolidate all good survivors into one clean shortlist.
Defaults
Use these unless the user overrides them:
| Constraint |
Default |
Notes |
| Language |
Internationally brandable |
Prefer names that travel well across markets. Use local-language roots only if the user asks or the market clearly needs them. |
| Primary TLD |
Market-dependent |
Global products → widely recognized commercial TLD such as .com. Local-first products → relevant country-code TLD. |
| Secondary TLDs |
Optional |
Other common or market-relevant TLDs when the primary is scarce. |
| Price |
Regular retail only |
Reject premium, reserved, auction, and broker listings. |
| Volume |
High |
Large candidate pool, verified survivors, clear top shortlist. |
| Code changes |
None |
Naming research is read-only by default. |
Naming Quality Bar
Prefer names that are:
- Brandable, not descriptive mush
- Easy to pronounce after one hearing
- Short when possible, or clean short compounds
- Distinct from known products in the same category
- Strong enough for a homepage, logo, and spoken conversation
Generate variety every round. Mix styles such as:
- Invented or coined words
- Prefix + root
- Root + suffix
- Short multi-word compounds
- Metaphor or motif pairings when they fit the product
- Short stems that can later carry a fuller meaning
Avoid unless requested:
- Hard-to-pronounce letter salad
- Generic category labels bolted together
- One naming family repeated endlessly
- Overused short affixes that are usually taken, unless verified free
- Local-language or niche cultural names the user did not ask for
References
Read references/research-playbook.md for the full research process, verification methods, collision checks, output tables, iteration rules, and anti-patterns.
1---2name: domain-name-suggestor3description: Research and suggest brandable product, app, or company names with live domain availability and collision checks. Use when the user wants domain name ideas, brandable names, available domains, TLD checks, naming shortlists, trademark/business collision scans, or runs /domain-name-suggestor.4---56# Domain Name Suggestor78## Overview910Use this skill to research brand names and domains for a product, app, or company. Deliver a large, varied shortlist where each finalist is brandable, easy to pronounce, actually registrable at regular retail price, and free of obvious product or business collisions.1112Research only. Do not change project code, rename folders, register domains, or commit unless the user explicitly asks.1314## Workflow15161. Gather context:17 - Product one-liner, audience, market geography, existing brand motifs, liked or rejected names.18 - If a project path is provided, audit the product from the codebase or docs first.19 - Infer only from observable evidence. Do not invent product claims.20212. Confirm constraints, then state the defaults you will use:22 - Language and naming style23 - Primary and secondary TLDs24 - Quantity target25 - Any hard exclusions from the user26273. Generate widely across multiple naming styles. Cull weak ideas before availability checks. Choose prefixes, suffixes, metaphors, and constructions yourself based on the product and market. Do not rely on a fixed shortlist of affixes.28294. Verify domain availability live with **registry RDAP first**. Prefer the official registry endpoint for the TLD when known; otherwise use a public RDAP bootstrap or lookup service. Treat `200` as taken and `404` as not registered. Fall back to registry WHOIS when RDAP is missing. Never use DNS alone. Never mark a name available from memory. Confirm finalists are regular retail price at a registrar, not premium.30315. Collision-check serious candidates and all finalists:32 - Exact-name web search33 - Apps, SaaS products, companies, and famous brands34 - Lightweight trademark risk flags35 - Crowded exact-name search results36376. Present results as:38 - Top picks with one-line rationale39 - Categorized full verified table40 - Method notes for how availability was checked41 - Optional short near-miss section only if useful42437. Iterate hard on feedback. If the user rejects a batch, change direction instead of defending weak names. When asked for finals, consolidate all good survivors into one clean shortlist.4445## Defaults4647Use these unless the user overrides them:4849| Constraint | Default | Notes |50|---|---|---|51| Language | Internationally brandable | Prefer names that travel well across markets. Use local-language roots only if the user asks or the market clearly needs them. |52| Primary TLD | Market-dependent | Global products → widely recognized commercial TLD such as `.com`. Local-first products → relevant country-code TLD. |53| Secondary TLDs | Optional | Other common or market-relevant TLDs when the primary is scarce. |54| Price | Regular retail only | Reject premium, reserved, auction, and broker listings. |55| Volume | High | Large candidate pool, verified survivors, clear top shortlist. |56| Code changes | None | Naming research is read-only by default. |5758## Naming Quality Bar5960Prefer names that are:6162- Brandable, not descriptive mush63- Easy to pronounce after one hearing64- Short when possible, or clean short compounds65- Distinct from known products in the same category66- Strong enough for a homepage, logo, and spoken conversation6768Generate variety every round. Mix styles such as:69701. Invented or coined words712. Prefix + root723. Root + suffix734. Short multi-word compounds745. Metaphor or motif pairings when they fit the product756. Short stems that can later carry a fuller meaning7677Avoid unless requested:7879- Hard-to-pronounce letter salad80- Generic category labels bolted together81- One naming family repeated endlessly82- Overused short affixes that are usually taken, unless verified free83- Local-language or niche cultural names the user did not ask for8485## References8687Read `references/research-playbook.md` for the full research process, verification methods, collision checks, output tables, iteration rules, and anti-patterns.
deepakness