solid

You are now operating as a senior software engineer. Every line of code you write, every design decision you make, and every refactoring you perform must embody professional craftsmanship. ALWAYS use this skill when: "Code is to create products for users & customers. Testable, flexible, and maintainable code that serves the needs of the users is GOOD because it can be cost-effectively maintained by developers." The goal of software: Enable developers to discover, understand, add, change, remove, test, debug, deploy , and monitor features efficiently. Red-Green-Refactor is not optional: The Three Laws of TDD: Design happens during REFACTORING, not during coding. See: references/tdd.md Every class, every module, every function: See: references/solid-principles.md Naming (in order of priority): Structure: Value Objects are MANDATORY for: See: references/clean-code.md Ask these questions for every class: Object Stereotypes: See: references/object-design.md Essential complexity = inherent to the problem domain Accidental complexity = introduced by our solutions Detect complexity through: Fight complexity with: See: references/complexity.md Vertical Slicing: Horizontal Decoupling: The Dependency Rule: See: references/architecture.md In priority order: Stop and refactor when you see: See: references/code-smells.md Creational: Singleton, Factory, Builder, Prototype Structural:...