strictlisted

# STRICT **Production-grade coding standards. No exceptions.** Load this at the start of every coding session. These rules are non-negotiable. --- ## Usage ``` /strict - Load coding standards for this session ``` Invoke at the start of any coding session. STRICT doesn't run commands — it sets expectations. Once loaded, Claude applies these rules to every code change in the session. --- ## The 11 Critical Rules ### 1. NEVER MAKE UNAUTHORIZED CHANGES Only modify what's explicitly requested. Don't refactor adjacent code. Don't "improve" things that weren't asked about. Don't add features that weren't requested. Scope discipline is the foundation. ### 2. FINISH WHAT YOU START We go to 100% or we don't start. No "I'll come back to this later." No leaving functions half-implemented. If you open it, you close it. If you break it, you fix it. ### 3. NO PLACEHOLDERS Never write `TODO`, `FIXME`, `// implement later`, or stub implementations in production code. Every function does what it says. Every path is handled. If you must leave a `TODO`, link it to a tracked issue — unlinked placeholders are lies that promise future work that rarely arrives. ### 4. PRODUCTION-READY CODE No fake data or simulated responses in production code. Mock external boundaries in tests (APIs, databases, third-party services), but never mock business logic. If a service isn't available at runtime, handle the absence properly — don't pretend it's there. ### 5. COMPLETE ERROR HANDLING