README-to-brief
Inspect the exact bounded project context before any hosted model work begins.
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. Add the audience, problem, or differentiator—or paste a full README.
Try an example
Next: review the brief and all checks.com + .app + .io + .ai selected · matching handles remain optional
How project context and learning data are handled
The visible text or one fetched public page is capped and screened first. A user-selected public page may be sent to the configured model provider to infer an evidence-grounded brief; pasted and uploaded text stays on the deterministic compiler at this step. No repository clone, source tree, `.env`, credentials, dependencies, or private-network URL. When you sign in, your full sprint is saved privately to your account. NamingSignal separately records the names shown, bounded brief labels, domain evidence, shortlist/reject/winner actions, and registrar-link clicks to improve future results; raw pasted or uploaded source text is not copied into that internal learning ledger. Exact domain checks may be reused until their displayed evidence becomes stale.