Skip to content

Repo name generator

Describe it in a sentence. Get six names, each with its reasoning.

Mention what it is (CLI, library, service) and what it works on.

Tone
Try an example

Suggestions

Your names show up here. Pick an example to see it in action.

How it works

A small, deterministic TypeScript module you can reason about. No AI API, no server, no tracking.

Reads your description

Matches your words against about forty software domains, detects the project type (CLI, library, service, dashboard), and lifts verb-object phrases straight from your sentence.

Applies six naming strategies

Descriptive, compound, action, hybrid, metaphor, and coined. Every metaphor carries its own reason, so each suggestion comes with an explanation that actually says something.

Scores and picks a spread

Candidates are scored for your chosen tone, length, and pronounceability, then selected for variety. Same input and seed always give the same result, so links are shareable.

Common questions

Does my description get sent anywhere?

No. The generator is plain TypeScript running in your browser. There is no API call, no AI model, and nothing is logged. The only time a request leaves your machine is when you click an availability link.

How are the names generated?

Your description is matched against a vocabulary of about forty software domains, and verb-object phrases are pulled from your own wording. Six naming strategies produce candidates, which are scored for tone, length, and pronounceability. The final set is picked for variety, so you see different styles side by side.

Are these names available?

Possibly not. Each suggestion links to GitHub, npm, and PyPI so you can check in one click. Coined and hybrid names are the most likely to be free; single dictionary words are the most likely to be taken.

What makes a good repository name?

Short, lowercase, hyphen-separated, and easy to say out loud. Internal tools should lean literal so teammates can find them. Public projects and packages benefit from something distinctive enough to search for and claim across registries.

Naming is the easy part. Shipping it is the job, from architecture to production.

Talk to an engineer

New tools, when they ship. One email per tool.