software-design-patterns-and-clean-code

What problem does it solve?

This Skill reduces maintenance risk and engineering churn by ensuring every change follows pragmatic design patterns, SOLID principles, and Clean Code practices that keep logic readable, separated, and easy to test.

Core Features & Use Cases

• Pragmatic patterns and SOLID: Apply design patterns only when they reduce real complexity and improve clarity or testability, with special focus on Single Responsibility and Dependency Inversion.
• Separation of concerns: Maintain clear boundaries between orchestration, domain logic, validation, persistence, formatting, and side effects so behavior is predictable and reviewable.
• Testable, minimal side effects: Prefer small composable functions and pure functions for transforms and validation, localize side effects, and add explicit error handling with actionable context.
• Use Case: Refactoring authentication/authorization utilities or debugging token/password logic by restructuring code into testable units without broad unrelated rewrites.

Quick Start

Use this skill before coding, refactoring, debugging, or reviewing changes in this repository to align the implementation with pragmatic design patterns, SOLID, and Clean Code, while keeping changes focused and safely testable.