What problem does it solve? Build-time invariants that exist only as prose documentation drift silently out of sync with the codebase. This Skill turns a rule into an enforced validator or generator script that fails the build when the invariant breaks, so guarded facts can never regress unnoticed. ## Core Features & Use Cases - Validator and generator authoring: Creates scripts under scripts/ following the repo's doc-block, CRLF-normalization, and portable-path conventions, including the regenerate-and-byte-compare pattern for generated surfaces. - Build chain wiring: Places the script in the correct slot — the validate-registry chain, the post-website-build verify slot, or run-on-demand — and syncs the website's predev/prebuild subsets and CI. - Documentation closure: Adds the registry row or CLAUDE.md entry that records the new guard, then verifies by breaking the invariant on purpose. - Use Case: When asked to "build-enforce that every component has a registry entry", the Skill writes the validator, chains it into validate-registry, and confirms it fails on a deliberately broken invariant. ## Quick Start Ask the AI to add a validator that fails the build when a specific invariant breaks, and have it wired into the validate-registry chain.
