mobile-first-site-proof

Files (1)

• SKILL.md

SKILL.md (first lines)

# Mobile-First Site Proof

Use this skill for the final release-readiness and production-proof pass on a website or web app. The full owner-supplied operating contract is `../../factory/icm/template/references/MISSION-V2-MOBILE-FIRST-SITE-PROOF.md`.

## Procedure

1. Write the operating contract before editing: mode, outcome, target, constraints, content policy, proof, ownership and commercial value.
2. Build the surface -> component -> handler -> route/service -> destination map and classify every important path.
3. Capture and inspect the live baseline at every required viewport. Inspect pixels, DOM state, console, targets and real interactions.
4. Repair truth/conversion first, then mobile structure, interactions, bounded motion, performance and release behavior in reversible slices.
5. Run every applicable item in the required static, route, browser, viewport, accessibility, performance, visual and deployment proof matrix.
6. Preserve unknown owner-controlled destinations as `UNVERIFIED`; never invent or overwrite them. Public/release-affecting `UNVERIFIED` items must be resolved, removed, or explicitly retained outside the released scope.
7. Obtain an independent review score of at least 8.5/10 with no unresolved P0/P1 issue.
8. Write the exact-candidate `docs/evidence/mission-v2-release.json` receipt and final report. Production can be called verified only after the exact deployed revision and actual target pass live checks.

## Completion

The skill can return `READY FOR PREVIEW`, `PREVIEW VERIFIED`, or `PRODUCTION VERIFIED` only at the evidence level actually reached. A build, screenshot, preview, deployment request, or provider READY message cannot prove production.

From executiveusa/vibe-engineering, MIT.

More from executiveusa/vibe-engineering