software-architecture

Clean architecture and hexagonal architecture both enforce dependency inversion and boundary translation, but the right choice depends on your domain complexity, coupling, and runtime behavior. This Skill analyzes your specific dependencies to recommend the lightest structure that fits.

Defining module boundaries requires explicit handling of coupling, cohesion, and dependency direction to prevent cycles. This Skill assesses your current codebase and recommends the simplest architecture that fits your business rules and change patterns.

Splitting a layered architecture into a modular monolith or microservices is needed when code becomes hard to change or test. This Skill evaluates your cross-cutting concerns and over-engineering tradeoffs to determine if a structural split is justified.

Selecting runtime patterns for state management and async workflows involves choosing between strategy, command, observer, state machine, pooling, and memoization patterns. This Skill matches the appropriate runtime pattern to your specific architectural structure.

Adding ports and adapters introduces accidental complexity through boundary translation and strict dependency inversion, which may be unnecessary for simple domains. This Skill helps steer decisions to reduce accidental complexity by recommending the lightest fitting structure.