architecture

You can document project architecture patterns and boundaries by using a guided mode to identify layers and dependencies, then recording decisions in patterns-architecture.md. This file acts as the canonical source of truth for design decisions across backend, frontend, and DevOps environments.

The best way to extract module boundaries in an existing codebase is through a guided extraction mode that analyzes dependencies and layers. It updates your architecture documentation and triggers an architecture decision record to maintain a coherent source of truth.

To update architecture documentation when adding a new domain or module, use the add-domain or add-module mode. This guides you through targeted questions, updates the architecture patterns file, and generates changelog and ADR triggers to reflect the new boundaries.

You need an architecture decision record when creating, updating, or extracting project patterns and boundaries. The process automatically triggers ADR generation alongside changelog updates to ensure architectural changes are tracked and reasoned about systematically.

Yes, you can use a single architecture file for both backend and frontend design decisions. The patterns-architecture.md file serves as a coherent source of truth for architectural patterns and boundaries across backend, frontend, and DevOps domains.