Silencer

Use when you need to drive the Silencer game from a terminal — clicking menus, taking screenshots, reading game state, validating game-data JSON, rebinding controls, or filling a lobby with fake authenticated players for multiplayer dev — without a human at the keyboard.

Use when Codex must compare screenshots, video grabs, UI captures, sprite references, design mocks, or visual regression outputs. Before judging visual correctness, stitch reference and current images into one side-by-side composite, inspect that single composite, and report concrete mismatches in layout, scale, crop, text, color, focus state, sprites, and missing or extra elements.

Use when you need to compare the current branch's UI against a baseline (origin/main or any ref) across every reachable user journey — main menu, options tabs, lobby connect, in-game HUD and overlays. Captures screenshots on both sides, builds side-by-side composites, runs pixdiff. Catches regressions that unit tests, E2E scripts, and architecture-boundary tests miss — e.g. garbled text from string-arena lifetime bugs, button-shape divergences, layout drift.