verification-checklist

name	verification-checklist
description	Code-generation verification skill. Use only when finishing a repo code change, validating generated code, or deciding which checks must run before presenting work.
metadata	{"family":"quality","owner":"quality + engineering","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"}

Verification Checklist

This is a code-generation skill. Use it only to validate implementation work.

Use When

• finishing a task
• deciding which checks to run
• verifying AI-generated code
• reviewing whether a page/build/SEO change is safe

Default Checks

Run these unless the task is clearly docs-only:

1. pnpm check
2. pnpm typecheck
3. pnpm test:unit
4. pnpm build

Additional Checks

Run these when relevant:

• pnpm smoke for public routing/rendering changes and broad built route coverage
• pnpm seo:audit for metadata, schema, canonical, or sitemap changes
• pnpm audit:responsive for ANY change that touches a public route, page template, tool client, or shared UI component (mandatory mobile responsiveness gate)
• pnpm audit:axe for changes that affect accessibility surface (forms, ARIA, semantics)
• pnpm audit:visual for visual regressions on the calculator and tools index

Mobile Responsiveness (Mandatory For UI Changes)

Mobile-first is a non-negotiable acceptance criterion for this codebase.

For UI work (any change that adds or modifies pages, components, layout, tools, or templates):

1. Start pnpm dev (or use the running dev server).
2. Run pnpm audit:responsive (writes a report under reports/audits/responsive/<label>).
3. Fix every CRITICAL finding (horizontal overflow, unscrollable tables, load errors).
4. Triage MAJOR findings (small touch targets) and resolve those that affect primary actions.

The audit is automated; do not skip it. If a route is intentionally excluded from the audit, document why in the PR.

Hook Alignment

• If the repo uses lefthook or another pre-push gate, keep the hook command list aligned with the required verification stack.
• When you change verification scripts or hook behavior, run the relevant hook path explicitly before finishing.

Minimum Review Before Finishing

Confirm:

1. file placement matches current architecture
2. route files stayed thin
3. pure feature logic lives outside bulky JSX/client components when it does not need React
4. calculator/tool/business rules touched by the change have unit coverage
5. metadata/schema patterns match current helpers
6. no retired path was used for new code
7. client/server split still makes sense

Reporting Rule

When reporting completion:

• say what checks ran
• say what did not run
• say if verification was skipped because the task was docs-only