Architecture

Build the smallest architecture that keeps business rules explicit and replaceable.

Use this skill for business-heavy systems, framework decoupling, integration seams, or domain boundaries. For straightforward CRUD, retain the codebase’s existing module structure and add layers only when an observable boundary needs one.

Architecture loop

1. Map the domain.

   Name the business capability, actors, invariants, state changes, inputs, outputs, and external systems. Split terms that mean different things in different parts of the product into bounded contexts.

   Done when every changed rule has one owner and a shared vocabulary.