B-J2KF-tighter-standard-verification-via-bully-style-edit-time
Standards under docs/planning/standards/ (S-NNNN, with applies_to.paths scope) are currently verified loosely — mostly at review time or via ad-hoc lint scripts. Investigate enforcing them at edit time with something like dynamik-dev/bully: a PostToolUse hook for Claude Code that runs deterministic checks first (linters, scripts, AST patterns) then LLM-based evaluation of plain-English semantic rules against each code change, blocking edits that violate configured standards. Our standards entities are a natural rule source — each standard’s Rule/How-to-apply prose plus its applies_to.paths scope could feed the hook’s config, giving immediate in-session feedback instead of deferred review findings.