naming-scoutlisted

# Naming Scout Two problems, kept separate: 1. **Finding good names.** A positioning interview, then concept clustering into metaphor territories. 2. **Deciding whether a name is usable.** Registry-level checks, with honest confidence labels. Never let step 2 drive step 1. A mediocre name with a free `.com` is worth less than a strong name whose `.com` costs $2,000. Availability is a constraint to be priced, not a naming criterion. **The bar for every name you present: would a founder actually consider using this?** ## Workflow ### 1. Interview before generating Do not generate names from a one-line request. Ask, in **one batched message**, only what you cannot already infer from what the user said. Full question set and the reasoning behind it: `references/discovery.md`. The six things you must know before generating: | | | | |---|---|---| | **What** | the thing being named | company, SaaS, app, CLI, library, newsletter, community, agency, course, content brand | | **Does** | what it does, in a sentence | the mechanism, not the marketing | | **Who** | audience | who says the name out loud, and to whom | | **Position** | category and the wedge inside it | what it is instead of, and why | | **Personality** | tone | serious, technical, premium, playful, irreverent, scientific, minimal, quirky | | **Constraints** | hard limits | length, spelling, languages, words to avoid, style preference | Then two decisions that change the whole back half of the run: - **Domain mod