component-architecture

To define component interfaces without code, outline module responsibilities and public contracts in design.md and interfaces.md files. This approach captures schemas and interface boundaries at the architectural level, separating logical design from implementation details.

Standardize component design documentation by generating artifacts like design.md, interfaces.md, and schemas.md under a .specs/ directory. This enforces consistent governance, accountability, and reusable component descriptions across multiple architecture projects.

Create architecture decision records (ADRs) alongside test-scenarios.md and design artifacts in the .specs/ directory. This enforces governance by documenting accountability, interface contracts, and logical component designs for review.

Component architecture design requires no specific frameworks or dependencies. It focuses purely on logical blueprints, defining WHAT modules do through interfaces and data schemas to guide implementation rather than relying on code libraries.

Use logical component blueprints when you need to standardize interfaces, data schemas, and module responsibilities across teams before coding. This approach ensures consistent development and enables architecture governance reviews without implementation constraints.