Orthogonality Principle
Design decoupled, independent system components to ensure changes in one module do not trigger unexpected ripple effects elsewhere.
The Orthogonality Principle skill provides a framework for building software systems where components are independent and non-overlapping. By emphasizing separation of concerns, interface segregation, and event-driven architectures, this skill helps developers eliminate 'shotgun surgery' and change amplification. It is particularly useful during the architectural design phase or during refactoring to transform tightly coupled monoliths into maintainable, testable, and reusable modules across diverse tech stacks like Elixir and TypeScript.
主な機能
01Implementation patterns for Separation of Concerns and Dependency Injection
02Identification of non-orthogonal red flags like tight coupling and duplicate logic
03Guidance on Interface Segregation to create focused, minimal APIs
04Strategies for Event-Driven Architecture to decouple services
0539 GitHub stars
06Data orthogonality techniques to maintain a single source of truth
ユースケース
01Refactoring complex controllers into independent, testable service modules
02Designing robust APIs where parameters and return values are localized
03Resolving cascading bug patterns by decoupling unrelated business logic