RestoreAssist

Use when producing, scripting, or shipping the RestoreAssist onboarding + walkthrough video SERIES as a batch (not one clip) — the setup-wizard / getting-started tutorial / onboarding-welcome videos need scripts written, narrated, rendered, captioned, and wired into the live app for distribution; when picking up where a prior session left off across many slugs; or when a polished walkthrough must land on YouTube and resolve in <VideoExplainer>.

Catch the "green locally, red in CI" failure class BEFORE pushing. Use whenever you are about to claim tests pass, before a PR, or when CI "Quality Checks" fails on a test that passed (or was skipped) on your machine — especially anything under lib/setup, app/api/setup, app/api/webhooks/stripe, app/api/oauth, or DB-touching code.

Capture browser screenshots for visual design verification (DESIGN.md Verification Gate). Use when a UI change needs an actual rendered screenshot — de-gradient passes, layout/spacing checks, light/dark comparison — rather than a static class diff. Covers the managed/remote-env quirks (browser install via resumable download, full-chrome headless launch, localhost-only page loads).

Diagnose and recover from blocked or failing production deploys — especially Prisma schema-drift / no-op'd-migration build failures on Vercel. Use when a deploy fails, a PR merge is "blocked", a build errors, or someone says "check logs", "failed", "deploy stuck", or "waiting for vercel".

Use at the start of every non-trivial user request and at any feature-completion / context-45%+ checkpoint. Forces a "Translation Blueprint" interception before code, enforces Service Layer separation, runs an automatic structural audit on completed features, and generates a dense session_manifest.md when context budget approaches the compaction threshold. Applies portfolio-wide; install per repo by reading this skill once and following the four phases exactly.

Use when designing or refactoring an API surface where the route handler / Convex action / framework endpoint has accumulated runtime mechanics (provisioning, credential reads, validation, readiness checks, restart/teardown helpers, integration fan-out). Separates the orchestration layer (auth, ownership, status transitions, audit events, persistence, user-facing error policy) from service modules (reusable runtime mechanics that return structured results). Substrate-agnostic — applies to Convex actions, Next.js App Router API route handlers / Server Actions, FastAPI endpoints, NestJS controllers, Express handlers.