Repository navigation
Rewrite the declarative templates as imperatives #2131
Description
Part of #2124.
The score PRs (#2107 to #2121) rewrote the templates under 95. The templates below score 95 or more but keep the older style, so an agent reads two dialects.
| Symptom | Example |
|---|---|
| Declarative bullet | backend/http.md:31 "Handlers are thin"; backend/database.md:7 "Migrations are committed" |
| Passive MUST | backend/monitoring.md:21 "Thresholds MUST be derived" |
| Em-dash clause | security/security.md throughout |
| Broken wrap | backend/caching.md:16-22, backend/messaging.md:10-12 |
| No blank line under a heading | backend/http.md, backend/monitoring.md, infra/containers.md |
Templates: security/security.md, backend/ http, auth, caching, database, grpc, jobs, messaging, monitoring, observability, data/ quality, migration, modeling, governance, infra/ containers, cicd, frontend/content.md.
Done when
- Each listed template uses imperatives, one PR per template
- No shipped section ID changes
Activity
braboj commentedon Oct 22, 2026
Constraint from a second agent review (2026-10-22): rewrite to imperatives without dropping a rule's condition or exception. Shorter is not the goal; a rule that loses when it applies is harder to apply correctly.