Use when resuming work in a repository after a human or another process may have edited the tree—diff from the recorded anchor, inspect untracked files, treat changes as intent, and rebuild the plan and verification baseline from current contents.
Use when diagnosing why a page or site may not be crawled, indexed, or understood by search engines: inspect robots, meta, canonical, sitemap, status, headings, internal links, and structured data; tie each recommendation to crawl, index, or intent without inventing ranking or traffic metrics.
Use immediately after one defect is confirmed to sweep for structurally related siblings across current code, history, copies, vendored forks, services, or languages; encode a repeatable Semgrep or AST query, gate each hit independently, and propose one root-cause fix.
Use immediately before declaring a task or session done—run the discipline checks that catch scope creep, leftover artifacts, unsolicited refactoring, and inflated prose, and block the completion claim on any failure unless the operator supplies a recorded override reason.
Use when raw footage or a rough assembly must become a finished video deliverable—establish the story spine, refine pacing and continuity, finish dialogue, music, and SFX to a loudness target, add readable titles and a consistent grade, then verify platform-specific exports. It owns edit-to-delivery finishing, not…
Use when analyzing why specific content spread or designing a platform-specific test of a sharing hypothesis—define cohorts, metrics, alternatives, confidence, and a stopping rule from observed data. Do not claim causality or access paid/credentialed analytics without the required gates.
Use when a known-good render and candidate captures must be compared reproducibly: lock viewport, scale, theme, locale, and time; mask declared dynamic regions; produce tolerance-bounded pixel/perceptual deltas; and classify each delta before replacing the reference set.
Use when a rendered UI has been built or changed and is about to be accepted — at the S4 Verify gate of a web, game, or other visual capability, before any ship step. Drives the "seen, driven, and measured" acceptance pass; the pixel-diff half belongs to visual-regression-baseline.
Use when a human or synthesized voice read needs performance direction before or across recording or generation passes—define character or brand intent, mark emphasis, pace, pauses, tone shifts, and pronunciation, then maintain continuity across takes. This skill shapes delivery; route identity clearance for the…
Use when a UI or media deliverable needs a criterion-by-criterion WCAG conformance decision, including keyboard, focus, accessibility-tree, contrast, reflow, motion, and screen-reader evidence. An automated score or screenshot alone cannot pass.