Rigor · olimxonuz0-lab bundle Use for any non-trivial coding, engineering, or deliverable-producing task — building a feature, fixing a bug, refactoring, designing an architecture, writing a script someone will run, or drafting a document someone will use. Enforces upfront planning before acting, rejects placeholder/stub/TODO code and unhandled edge cases, and cuts filler from responses so the final answer is dense and useful. Trigger whenever the user asks to build, implement, fix, refactor, design, migrate, optimize, or ship something — even without words like "production-ready" or "thorough." Also trigger when a task has enough moving parts that diving straight into output risks missing something (multi-file changes, unclear requirements, several edge cases, sub-steps). Do NOT trigger for single-line answers, quick lookups, casual conversation, or an explicitly requested rough/quick/throwaway draft.
