Base Code Doctrine

This skill defines the non-negotiable core principles governing all code modifications and creation. These philosophies override language-specific conveniences in favor of long-term maintainability.

The Iron Law

Code is written for humans first, machines second. Every architectural and syntactical decision must answer: "Will this still make sense in 6 months?"

Core Principles

1. Optimise for Readability & Maintainability: Avoid “clever” or esoteric code. Prefer boring, predictable patterns.
2. Clean & Lean Code: Let the code breathe. Do not cluster unrelated lines of code together. Group related logic, separate unrelated logic with blank lines.
3. Separation of Concerns: Avoid monolithic (God) files. Co-locate related logic where appropriate, but prevent tight coupling.

Naming Standards

• Intention-Revealing: Use highly descriptive names.
• Verbosely Clear: Functions should read like sentences (e.g., calculateUserDiscount() instead of calcDisc()).
• No Abbreviations: Unless universally understood (like id or url), do not abbreviate variables.