Software Architecture Skill
You've got a system to design or refactor. This skill cuts through the academic noise and gives you practical architecture decisions rooted in trade-offs, not dogma.
When to Use This Skill
- "How should I structure this?" — system decomposition, boundaries, layering
- "Should I use microservices/CQRS/event-driven?" — pattern selection with honest trade-offs
- "This code is becoming a mess" — coupling, cohesion, and refactoring strategy
- **SOLID vi
[Description truncada. Veja o README completo no GitHub.]