# Domain Name Suggestor

> 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.

- Skill: `deepakness/domain-name-suggestor` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add deepakness/domain-name-suggestor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/deepakness/domain-name-suggestor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: deepakness (https://skillmd.com/u/deepakness)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/deepakness/domain-name-suggestor

---


# 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

1. 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.

2. 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

3. 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.

4. 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.

5. 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

6. 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

7. 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:

1. Invented or coined words
2. Prefix + root
3. Root + suffix
4. Short multi-word compounds
5. Metaphor or motif pairings when they fit the product
6. 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.