dev-corelisted

# DEV-CORE - Core Coding Discipline ## Purpose Language-agnostic coding discipline for implementation work. It targets both failure modes of AI-generated code at once: - **Spaghetti (under-structure)**: tangled responsibilities, wrong placement, hidden coupling, copy-pasted rules. - **Over-engineering (over-structure)**: speculative layers, pass-through files, a framework built for a one-off change. Good code sits between them: the smallest complete change, placed correctly, that the next requirement extends instead of rewrites. **Strict Enforcement**: All rules in this skill are MANDATORY and NON-NEGOTIABLE whenever this skill is invoked. The agent must strictly enforce every requirement without taking shortcuts, guessing domain logic, or negotiating discipline away. ## Mindset: Code Audience & Zero-Shortcut Imperative Write code as if it will be reviewed and maintained by a ruthless, exhausted senior engineer who will reject any bloated diff or hidden complexity — write for long-term clarity, not quick compliance. If the change is not obvious, self-explanatory, and surgical on first read, it is unacceptable. - **Dual Maintainer Compatibility (Human & AI)**: Code is read by both humans (in MRs/code reviews) and future AI agents. It must be explicit, self-contained, and free of hidden coupling or implicit magic so any future maintainer — human or AI — can safely extend it in minutes without a rewrite. - **Zero Shortcuts**: Never choose a quick patch, dummy fallback, o