project-name-checklisted

Clear a name before it gets stamped into a repo, a package manifest, a domain, and a logo. The whole skill rests on one rule: **a name is only "available" where you checked it, with evidence you can show.** Registry APIs and RDAP answer definitively; search engines do not. Report what you verified, name what you could not, and never round an unchecked surface up to "free". You investigate and report. You do not register, purchase, publish, or reserve anything. This skill covers the surfaces a *shipped artifact* lives on. If the name is for a company, a product brand, or a storefront, the surfaces that decide it are social handles, commerce platforms, company registers, and trademarks: use the `business-name-check` skill for that, or run both when the project and the company share a name. ## Step 1: Frame the check Work out three things before searching. Infer what you can from the working directory (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `*.xcodeproj`, `manifest.json`, README, git remote) and only ask about what is genuinely unknowable. 1. **The candidates.** Push for three to five, not one. A single candidate turns this into a yes/no with no fallback, and the first choice is usually taken. If the user has only one, check it first and generate variants in step 5 if it fails. 2. **What ships, and where.** An npm package, a Homebrew CLI, a Mac App Store app, a VS Code extension, a Python library, a hosted product, or several at once. This picks the surfa