What problem does it solve? Verifying that a game engine faithfully implements a tabletop ruleset is tedious: rules live in PDFs, parameters live in JSON, and logic lives in GDScript, with no easy way to confirm they agree. This Skill cross-checks all three sources and produces a structured compliance checklist. ## Core Features & Use Cases - Rule-to-code mapping: Greps the rules PDF table of contents and changelist files, then locates the implementing functions in game_engine.gd and godot/game/. - Hardcoded constant detection: Flags rule parameters (like a panic threshold of 7) that should live in game/rulesets/*.json instead of engine code. - Checklist and findings output: Produces a table of Rule / Engine location / JSON-driven / Matches rules, plus grouped findings for mismatches and uncovered rules. - Use Case: Before adopting ruleset v18, run an audit scoped to melee to see which v17 mechanics are JSON-driven, which are hardcoded, and which v18 changelist items have no engine coverage yet. ## Quick Start Ask the AI to run a v17 ruleset compliance audit on the engine, scoped to all phases, and file issues for any hardcoded rule constants it finds.
