Communitygithub.com

web-launch-checklist

Use when building, changing, testing or launching a small web product (a static marketing site, a single-file PWA, or a paid microapp with a merchant of record such as Paddle): checks for the bugs that usually slip through (wrong-case paths, stale caches, drifted canonical URLs, hover states nobody tested, apps that never update), CI setup, and scripts that inspect the files and screenshot every page at phone, tablet and desktop widths.

Was ist web-launch-checklist?

web-launch-checklist is a Claude Code agent skill that use when building, changing, testing or launching a small web product (a static marketing site, a single-file PWA, or a paid microapp with a merchant of record such as Paddle): checks for the bugs that usually slip through (wrong-case paths, stale caches, drifted canonical URLs, hover states nobody tested, apps that never update), CI setup, and scripts that inspect the files and screenshot every page at phone, tablet and desktop widths.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/gabrielaoliveranz/claude-web-skills/tree/HEAD/web-launch-checklist

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Web launch checklist

Every item in this skill is a bug that really happened while building two websites and two apps (a consultancy website with 155 commits of CI history, a budgeting PWA, and a paid app with its own sales website). Use it to plan a change and to check it before saying it's done.

How to use it

  1. Read references/field-notes.md once per project, and references/building-an-app.md before starting a new app. Then find the parts of the task in the table below and read those reference files.
  2. While building, follow the rules in those files.
  3. Before saying "done", run the scripts below, look at the screenshots, and go through references/before-done.md.
If the task touches...Read
Starting a new app, its data or its logicreferences/building-an-app.md
Updates, reminders, PDF and Excel exports, imports, backups, insights in an app with no serverreferences/app-features.md
Domain, DNS, Cloudflare, email, Paddle, GitHub Pages, formsreferences/connecting-services.md
Translations, currencies, dates, holidaysreferences/i18n-architecture.md
An installable app, service worker or app versionreferences/pwa-releases.md
Forms, sheets, scrolling or anything on phonesreferences/phones.md
A new domain, an API call, moving the appreferences/csp-and-domains.md
Checkout, subscriptions, webhooks or pricingreferences/payments.md
Buttons built in JavaScript, or account statesreferences/app-code.md
A static site going live: sitemap, canonical URLs, share images, 404 page, Cloudflare quirks, caching, forms, honest contentreferences/static-site-checks.md
Setting up CI, or a check that fails (or passes) for the wrong reasonreferences/testing-and-ci.md
Several languages, including hreflang and canonical URLs for sites that switch with ?lang=references/multilingual.md
Hiding elements, gradient text, layout shiftsreferences/css-traps.md
Copy, figures, legal pagesreferences/content.md
Finishing any changereferences/before-done.md
Ready-made code: language links, demo links, app moves, checkout, webhooks, reminder emailsreferences/recipes.md
Every technical bug we hit (PWA, phones, data, SEO, CI, languages)references/field-notes.md

Scripts

Run them from the project folder, giving the script's full path. check-static.mjs and bump-version.mjs need only Node. The others use the project's Playwright (npm install -D playwright, then npx playwright install chromium).

ScriptWhat it catchesExample
check-static.mjsStraight from the files, no browser: paths with the wrong letter case (fine on Windows and Mac, 404 on the server), broken internal links, canonical / og:url / og:image / sitemap / robots.txt that disagree, share images whose real size differs from the declared one, a hand-copied footer that drifted on one page, mailto: forms, relative paths on the 404 page, relative fetch() calls in scripts, hreflang codes Google rejects (such as es-419) or a canonical that drops the other languages, width: 100vw, <style> in the body, skipped heading levels, published documents no page links to, untracked filesnode <skill>/scripts/check-static.mjs --same footer
check-pages.mjsIn a real browser at 320, 390, 820 and 1440 px, per language and colour scheme: sideways scroll, text cut off at an edge, a header that wraps, script and console errors, failed requests (including ones the CSP blocks), HTTP errors. Saves full-page screenshotsnode <skill>/scripts/check-pages.mjs --base http://localhost:8000 --pages index.html,pricing.html --langs en,pt-PT --schemes light,dark
check-states.mjsContrast of every link and button at rest, on hover, on keyboard focus and while pressed, against what is really painted behind the text; elements with no visible focusnode <skill>/scripts/check-states.mjs --base http://localhost:8000 --pages index.html
make-share-card.mjsRenders the link-preview image from assets/share-card.html (or your own template) at 1200x630 with the site's real fontsnode <skill>/scripts/make-share-card.mjs --template card.html --out assets/og.png
make-favicon.mjsBuilds the root favicon.ico (16, 32 and 48 px) from your SVG iconnode <skill>/scripts/make-favicon.mjs --svg assets/icon.svg --out favicon.ico
bump-version.mjsPWA: raises the version in version.json, the page and the sw.js cache name. Static site: sets a new ?v= on every local CSS and JS linknode <skill>/scripts/bump-version.mjs --dir public 1.4.0 or --dir . --assets 20261114a

check-pages.mjs also takes --reduced-motion (check nothing stays hidden with animations off), --widths and --header. check-static.mjs takes --ignore (path prefixes) and --strict (warnings fail too). Every script exits with 1 when it finds a problem, so they work in CI as they are.

Non-negotiables

  • Test languages through a local HTTP server, never file://.
  • Never tell users to delete or reinstall a home-screen app before they have a backup.
  • A webhook marked "succeeded" only means your endpoint answered. Open the payload.
  • Break a check on purpose once before trusting it.
  • Say plainly what you could not test.

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

Verwandte Skills