---
name: naming-and-domain-validation
description: Generate brand/product names and validate domain availability for Consumer AI ventures, especially when the user asks for app names, GoDaddy checks, or naming options tied to positioning.
---

# Naming and Domain Validation

Use this when Antoine asks for a product/app/company name, asks to check GoDaddy/domain availability, or needs a naming shortlist for a Consumer AI Factory venture.

## Principles

- Start from the product's emotional job, not the internal mechanism. Prefer names that describe the user's desired outcome over names that say "AI", "agent", or a feature.
- Avoid generic AI-wrapper naming unless the category specifically benefits from it. Names like `SomethingAI` are usually a fallback, not the first choice.
- Prefer credible, human, distribution-friendly names that can survive if the wedge expands.
- Keep the answer decisive: give one recommended name, then a compact ranked backup list.
- Distinguish registry availability from GoDaddy cart availability. If GoDaddy blocks automation or cannot be checked, say so plainly and use registry WHOIS/RDAP as a strong but not final signal.

## Workflow

1. Infer the positioning from the conversation:
   - target user
   - emotional job
   - concrete first value loop
   - likely distribution channel
   - whether the market language is US-specific or global
2. Generate candidates in several families:
   - outcome-led names (`NextMove`, `GetSeen`, `TrialReady`)
   - action-led names (`ReachClubs`, `PitchCoach`)
   - category-led names (`PlayerAgent`, `SquadIntro`)
   - trust/credential-led names if parents, coaches, or professionals are involved
3. Check exact-match `.com` first.
4. If `.com` is taken, check strong modifiers only when they improve meaning, not just because the domain is available.
5. Use WHOIS/RDAP as fallback validation when registrar pages block automated access.
6. Report results as:
   - recommended name
   - domain status and method used
   - why it fits
   - backup options
   - taken names to avoid if useful

## Domain checking commands

For `.com` names, registry WHOIS is usually fast and low-noise:

```bash
whois -h whois.verisign-grs.com example.com
```

Interpretation:

- `No match for` usually means available at the registry level.
- Presence of registrar/name-server/creation-date fields means taken.

For mixed TLDs:

```bash
whois example.app
whois example.ai
```

RDAP can be used too, but may timeout or rate-limit depending on host/network:

```bash
python3 - <<'PY'
import requests
for d in ['example.com']:
    r = requests.get('https://rdap.org/domain/' + d, timeout=10)
    print(d, r.status_code, r.text[:200])
PY
```

## Pitfalls

- Do not claim "available on GoDaddy" unless GoDaddy was actually checked. Say "appears available by registry WHOIS; confirm in GoDaddy before buying."
- Do not stop at the first taken domain. Generate adjacent names and check them.
- Do not over-index on `.ai` if the buyer/user is not buying AI; use `.com` for consumer credibility when possible.
- Do not pick names that narrow the product too early unless the wedge benefits from the constraint.
- Watch geography language: `tryout` and `soccer` skew US; `trial` and `football` fit global football better.

## References

- See `references/player-career-agent-naming.md` for an example session checking names for a football player outreach/trial-invite app, including GoDaddy-blocked fallback handling.