launch-check
Skill2 starsChanged 17 days agoMITView on GitHub
Make a website ready to launch, covering SEO, social sharing, crawler files, a custom 404, accessibility basics, console errors, bundle size and leftover template defaults. Use before shipping or launching any website or web app, or when asked to audit one for launch readiness.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- craigcossairt/trellistheir own version, first seen Nov 6, 2026
- Ces107/agent-forgetheir own version, first seen Oct 25, 2026
- lfxiui/usefulmint-skillstheir own version, first seen Oct 20, 2026
- matt-warchol/launch-checktheir own version, first seen Oct 20, 2026
- path-to-ai-com/ptai-ecom-toolkittheir own version, first seen Oct 15, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use setup.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- me2resh/apexyard★ 542same name
- craigcossairt/trellis★ 5same name
- matt-warchol/launch-check★ 1same name
- 20030419zhanghongyi/AI-Software-Engineering-Workflow-Template★ 0same name
- Ces107/agent-forge★ 0same name
- lfxiui/usefulmint-skills★ 0same name
- path-to-ai-com/ptai-ecom-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- dev-setupSkill
- ui-sourcesSkill
- web-tasteSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run node <path>/check-launch.mjs <preview url> [--public] [--local-business[=<schema type>]] [--max-js-kb=<n>].
- Very specific: line 49
Add one end-to-end test (Playwright if the project has it) that opens every page from the sitemap, or the main routes for an internal app, …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch check
A site is ready to launch when scripts/check-launch.mjs passes against a production preview, the console-error test passes, and the review list below holds.
Run it
- Build for production and start the production preview server (for example
vite preview,next start,astro preview), not the dev server. - Run
node <path>/check-launch.mjs <preview url> [--public] [--local-business[=<schema type>]] [--max-js-kb=<n>]. It crawls the home page, every internal link and the sitemap, and exits 1 on any problem.--publicfor a public website. Leave it off for internal tools, dashboards and local apps.--local-businesswhen the site is for a local business. Pass the schema.org type if it's more specific, for example--local-business=Restaurant.--max-js-kbsets the gzipped size budget per script (default 200).
What it checks
Every site:
| Id | Rule |
default-title | No template title like "Vite + React", "Create Next App" or an empty title |
placeholder | No lorem ipsum, "your company here", placeholder text or TODO on any page |
source-map | No source maps served in production. Turn them off in the build config |
bundle-size | Every script is within the budget. Split routes, lazy-load heavy parts, drop unused dependencies |
Public sites (--public) also:
| Id | Rule |
empty-shell | The page source has real content: render on the server or prerender, so crawlers and link previews see it |
duplicate-title, meta-description, duplicate-description | Every page has its own title and meta description |
canonical | Every page has an absolute canonical link |
one-h1 | Exactly one h1 per page |
og-image | Every page has a social share image (og:image, 1200×630) |
alt-text | Every image has an alt attribute |
orphan-page | Every page is linked from another page |
site-file, sitemap | robots.txt, a sitemap.xml that lists the pages, and llms.txt |
favicon | A favicon |
structured-data | JSON-LD structured data on the home page |
local-business | The LocalBusiness schema (or the given type), with --local-business |
not-found | Unknown URLs return a real 404 status with a custom page that links home |
Console errors
Add one end-to-end test (Playwright if the project has it) that opens every page from the sitemap, or the main routes for an internal app, and fails on any console.error or uncaught page error.
Review what the script can't
- Alt text describes the image; decorative images use
alt="". - Pages nested more than one level deep have breadcrumbs, with
BreadcrumbListstructured data. - Internal links help a reader move on: related pages link to each other, not only from the nav.
- Structured data matches the page. LocalBusiness name, address, phone and hours are the owner's real details.
robots.txtpoints to the sitemap, and the sitemap uses the canonical domain.llms.txtdescribes the site and links its key pages.- The browser tab title and the favicon are the product's own on every page, including the 404.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.