namekit

Name a project against a convention rather than a blank page, and hand back only names that are actually free. Two explicit modes:

• generate. Turn a project description into a ranked shortlist of names built to the user's naming convention, then probe the two or three the user picks against the domain, npm, and GitHub namespaces and crown one.
• check. Take names the user already has and report whether each one is free. No generation.

The reason this is a skill and not a one-line ask: left alone, a model returns ten spellings of one idea, invents a convention nobody uses, and never checks whether any candidate is taken. namekit fixes all three, in that order.

When this fires

• generate. "Name this project", "what should I call this", "give me name ideas", "come up with a name for X", "I need a name for my new SaaS".
• check. "Is growaloy taken", "check if this name is available", "did anyone grab this npm package".

An ask that supplies a description gets generate. An ask that supplies names gets check. When the user supplies both, run check on their names first, then offer generate, because a name they already like outranks anything you invent.

The probes (both modes)

Three namespaces, three commands. Each one is a public HTTP contract, so it is safe to pin.