What problem does it solve? Safety rules that live only in checklists or documentation get silently deleted during refactors, and in a livestock record app a defect can hurt someone who is not the user. This Skill pushes each of the five spec §12 rules up a mechanism ladder — unrepresentable, unconstructible, unpersistable, source-text test, documented — so a rule cannot be weakened without failing a gate. ## Core Features & Use Cases - Mechanism-level enforcement: Maps each rule (never default a withdrawal, never give veterinary advice, never a compliance record, never silently correct, honest timestamps) to concrete Dart types, SQL CHECK constraints, and layer bans. - Two-way self-testing policy guards: ContentPolicy regexes over lib/**.dart and ARB files ship with planted offenders and legitimate-copy cases so a guard that never fires is detected. - Use Case: Before adding a default value, pre-fill, suggestion, hint text, or edit verb to the Flutter app, check this Skill to confirm the change does not drop a safety rule from unconstructible down to merely documented. ## Quick Start Before adding any default, pre-fill, suggestion, validation, or edit path to the app, apply the shed-safety-rules skill to verify the change keeps every §12 rule at its current mechanism level or higher.
