NamingSignalalpha

Project name generator · README-ready

Turn a real project brief into names worth shipping.

Give NamingSignal the problem, mechanism, audience, and future scope, or start with the README you already wrote. It extracts an editable brief before generating, so the names reflect the project rather than a generic keyword cloud.

Step 1 · Your project

Describe what you’re naming

One sentence is enough. NamingSignal analyzes it, infers the brief, and checks availability in one run.

Saved in this browser
Try an example
0 / 250,000 bytes

Infers your target customer, desired outcome, and naming guidance from the description. Everything stays editable, and skipping it is fine: the same analysis runs automatically when you generate.

Checking .com · .app · .io · .ai · any ending can passDomain endings, search breadth, and handle checks
Customize
1. Which domain endings can win?

Select the endings you would genuinely launch on. Up to five can be checked in one run.

“Likely unregistered” is a calibrated registry signal at check time, not a purchase guarantee. Unsupported or timed-out checks stay unresolved.
2. How broad should the search be?

More candidates improve the odds in crowded domain namespaces.

FunctionalOutcomeMetaphorLateral
3. Which handles should we check?

Advisory only. A taken handle never blocks a name. GitHub gets an exact automated check, other platforms get one-click manual links, and the deep check suggests handle alternatives when the exact one is taken.

Your naming run

Generate 150 names · check 600 domainsAcross .com, .app, .io, .ai · keep names where at least one selected domain passes.
01

README-to-brief

Inspect the exact bounded project context before any hosted model work begins.

02

Developer namespace signals

Check GitHub, npm, and PyPI exact-name evidence alongside selected domain endings.

03

Portable decision record

Export the brief, candidates, evidence, shortlist, and remaining manual actions for the team.

Practical answers

Before you name, check, or ship

Availability is time-sensitive evidence. A final choice still needs current registrar verification, spoken testing, cultural review where relevant, and appropriate legal clearance.

Can an agent use the project name generator?

Yes. The public REST contract, local CLI, and stdio MCP server expose the same bounded workflow for Codex, Claude, and other capable agents.

Does NamingSignal clone a private repository?

No. The web flow accepts bounded pasted or uploaded context and safe public imports. It excludes detected secrets and does not clone a private repository.

Can I rename an internal codename later?

Yes. The workflow preserves constraints and rejection reasons, so a team can rerun the sprint when the audience, scope, or public-launch requirements change.