noobnooc

better-codex

Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into user-facing UI.