Solid

This is the kind of skill you'd want if you're tired of shipping code that works today but becomes a maintenance nightmare tomorrow. It enforces TDD's red-green-refactor cycle as non-negotiable, applies all five SOLID principles to every class, and mandates wrapping primitives in value objects (no raw strings for user IDs or emails). The approach is prescriptive: one level of indentation per method, no else keywords, Rule of Three before removing duplication. It's opinionated about architecture too, pushing vertical slicing and the dependency rule. If you want guardrails that push you toward senior-level habits or you're refactoring a mess into something maintainable, this gives you a concrete process and catches code smells before they metastasize.