Site launch checklist

Walk release-critical routes, content, and navigation before launch.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Site launch checklist

Walk release-critical routes, content, and navigation before launch.

## Deliverable
A launch verification report with a focused patch and evidence for key routes.

## Stack and visual direction
- Recommended starting stack: Use the existing stack, browser tooling and the project's test commands. Capture before-and-after evidence.
- Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Use this direction for any new or revised UI within the agreed patch scope.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance.
  Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually.
- [Playwright Test](https://github.com/microsoft/playwright) (Repository) — Automate repeatable browser journeys using visible roles and assertions.
  Playwright-managed browser binaries. [Official setup](https://playwright.dev/docs/intro).
- [Lychee](https://github.com/lycheeverse/lychee) (Repository) — Check internal and external links and make transient failures distinguishable.
- [Lighthouse](https://github.com/GoogleChrome/lighthouse) (Repository) — Capture comparable page performance, SEO and accessibility diagnostics.

## Workflow
1. Inventory public routes, critical CTAs and destinations. Review metadata, images, favicon, mobile menu, link integrity, footer and custom 404, then fix the issues within scope.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] Primary journeys reach real destinations and verify form feedback and error states.
- [ ] Every reviewed page has a meaningful title and useful mobile layout.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Capture a reproducible baseline, validate the changed flow afterward, and report evidence and any findings still open.

Recipe resources

Source, setup, and compatibility details.