architecture-patterns

Design system architecture from user flows by enumerating user, admin, and system interactions to ground component responsibilities. This flow-first approach justifies architecture decisions and produces C4-aligned views with component proposals to avoid unnecessary complexity.

Analyze coupling to identify circular dependencies by mapping component interactions and enforcing dependency direction rules. This coupling detection process exposes hidden coupling and god objects, allowing you to prioritize structural refactors effectively.

Document architecture decisions for a refactor by producing structured decision records that compare options and trade-offs. This decision documentation process creates tracked tasks for design activities, ensuring every component maps to user, admin, or system flows.

Use this flow-first approach for API alignment and architecture reviews by mapping interactions to expose coupling issues and dependency-direction violations. It generates C4-aligned views and component proposals, ensuring structural problems are identified before refactoring.

Flow-first design for system architecture may not suit projects lacking clear user, admin, or system flows to map. If structural problems are absent and dependency direction is already enforced, the overhead of generating C4-aligned views and decision records may be unnecessary.