Run synchronized app visual-review tests, generate screenshots from the same live app state the user sees, and inspect those screenshots before completion claims.
Use when unit or integration tests emit source-space failure manifests and the user needs browser replay screenshots with markers showing where each failure appears in the app. Applies to canonical stroke tests and future geometry/UI tests that can map failures to fixture-local coordinates.
Enforce git/gh CLI separation rule for version control operations
Centralize and refactor constants/events/feature IDs, replace ad-hoc string literals, and maintain grouped+flattened constants contracts. Use when requests mention adding events/tools/features or reorganizing constants.
Apply deprecation lifecycle rules while preserving compatibility and documenting replacement owners/paths. Use when requests deprecate packages/APIs or retire legacy runtimes.
Synchronize implementation changes with framework/app docs contracts across API surfaces, behavior specs, and constraints. Use when code changes must be reflected in docs.
Author or refactor features with explicit priority/exclusive/session semantics and boundary-safe common-API usage. Use when requests add/fix feature behavior or session flow.
Audit and fix import-boundary violations with deterministic facade-first rewrites and explicit exceptions. Use when requests mention deep imports, boundary cleanup, or core-facade migration.