
Pre-Launch Site Check Kit is a vibe coding kit for Claude Code and Codex. Give it a URL, get a fix-ordered report of what launch misses. It includes 7 fixes for pitfalls the maker hit in real work. Free.
When this helps
You want to launch a site, but worried old test settings or placeholder text are still there
What it does
Checks a site for things that are easy to forget before launch — leftover noindex settings, staging URLs, http→https redirects, canonical tags, placeholder text, form destinations, broken links — against a fixed set of checks. The AI opens each flagged item on the real page and sorts it as confirmed, false positive, or needs-checking, then reports what must be fixed before launch first. For a staging site, give the production domain too, so leftover staging URLs can be found. Where a fix lives on the server, such as .htaccess, only the lines to change are given, so existing settings are never overwritten. What a machine can't check, like actually submitting a form, is handed over as a checklist.
The fixes baked into this kit
- Ordinary copy mis-flagged as placeholder textAny "here" followed by "insert" was caught as placeholder text, which also flagged normal explanatory copy. Narrowed it to only the patterns "will be inserted here", "is inserted", and "please insert".
- Intentional noindex pages flagged as "fix this"A single noindex page was treated as a leftover mistake, so login screens and pages intentionally kept out of search were flagged as "fix this" too. Now it only says "fix" when every page is noindex (a whole staging setup left in place); if only some pages are, it says "review" and asks whether that was intentional.
- WordPress-only guidance shown on non-WordPress sitesIt pointed non-WordPress sites to WordPress's "discourage search engines" setting. Now that guidance only appears when the page contains /wp-content/.
- href="#" menu buttons flagged as placeholder buttonsMany sites use href="#" for menu toggles, which flooded every page with "placeholder button" warnings. Now it's downgraded to "review" with a note that it's fine if it works as a button, and only up to 5 examples are shown.
- http-to-https redirect staying at 302On an Apache server, .htaccess's [R] defaults to a 302 (temporary) redirect. Now, on Apache, the fix suggestion explicitly says to change it to [R=301,L].
- Overwriting and erasing the live .htaccess on the serverTrying to fix the 302, there was no .htaccess in the site's repository — it only existed on the rental server. Uploading a local file would have overwritten and erased the server's settings. Now the server's existing file is opened and reviewed first, and only the lines to change are given.
- Check results almost leaking into the distributed zipCheck results were written inside the tool's own folder, so the checked site's URLs and form destinations nearly ended up in the distributed zip. The output location was moved to _work/, which is automatically excluded when the kit is packaged.
What's inside
- The flow (set 3 things → check → judge item by item → fix → report)
- A tool that checks a site (noindex, leftover staging URLs, redirects, canonical, placeholder text, forms, links...)
- A self-test for the tool (runs without touching the internet)
- A table of each check's confirm condition, common false positives and how to fix it
- Writing rules (never predict numbers, never say "no problems found", etc.)
- Ready-to-use phrases (when the production domain is unknown, when auth is blocking access, etc.)
- A pre-delivery checklist
File list (12)
- .gitignore
- AGENTS.md
- CLAUDE.md
- KIT.md
- NOTES.md
- rules/CHECK.md
- rules/FLOW.md
- rules/PROMPTS.md
- rules/SPEC.md
- rules/TONE.md
- tools/check-site.mjs
- tools/selftest.mjs
The first three decisions
- The site to check (its URL)
- Production domain (default: same as ①)
- How far to go (default: just the report)
What you need
- No extra costClaude Code or CodexEither works.
- No extra costNode.js 22 or newerTo run the checking tool. No extra installs needed.
- No extra costThe URL of the site to checkPages that need login, and the rendered content of JS-driven sites (SPAs), are out of scope.
How to use
Just paste this into your AI.
I want to use the nice to have kit "Pre-Launch Site Check Kit". Follow https://nicetohave.app/en/g/23EP4A36-•••••••••• and set it up.
Works the same in Claude Code or Codex.
Read what this tells your AI to do, before you paste it
If you would rather take the files yourself
Paste the line above and your AI fetches it. If your AI cannot fetch it, or you would rather download it yourself, start here.
- Unpack the zip you downloaded
- Open the resulting folder in Claude Code or Codex (in VS Code, "Open Folder")
- Type "start building with this kit". The instructions are inside (Claude Code reads
CLAUDE.md, Codex readsAGENTS.md)
FAQ
- What should I watch for when checking a staging site?
- Always give the production domain in step ②. If you don't, the staging URL itself gets treated as "production" and leftover staging URLs can't be found at all. If the address starts with stg. or dev., or ends in vercel.app and similar, you'll be asked for the production domain.
- Can it check a JavaScript-built site (an SPA)?
- Barely — it only reads the HTML before JavaScript renders it. If it reports reading just one page, this is usually why. Run it against each main page's URL one at a time instead.
- What about a staging site behind Basic Auth?
- It needs to be turned off just for the check. Never give the kit the ID and password. If it can't be turned off, you're told the check's coverage will be limited.
- Will it directly edit server config files like .htaccess?
- No. They can exist only on the server and not locally, and uploading over them could erase settings. The existing server file is opened and reviewed first, and only the lines to change are given.
- Can I trust everything the tool flags as "fix this"?
- No. The tool only guesses from the HTML, so it has false positives. The AI opens each flagged item on the real page and sorts it into confirmed, false positive, or needs-checking before it goes into the report.
Reviews
This is your kit. You can also see its reviews on your page.
No reviews yet. Be the first to say something.
Supporters
Once support opens, the people who backed this kit will be listed here.
- Publisher
teluki0815- Published
- 2026/11/16
- Price
- Free
- Category
- Delegate work
- Personal data
- Not handled
- Security review
- Not needed (no personal data)
- What's inside
More kits
shuto-shinoda2026/10/29
Misconduct & Incident Report KitFree
Talk through what happened, get separate misconduct and incident report drafts
shuto-shinoda2026/10/29
Subscription & Contract Ledger KitFree
Turns contracts into a ledger and lists cancellation deadlines soonest first
shuto-shinoda2026/10/29