design-architecture

What problem does it solve?

It helps you define macro-level system architecture—domain boundaries, data flows, and interaction contracts—so business logic stays vendor-neutral and operationally safe.

Core Features & Use Cases

• Hexagonal/Clean boundary design: Enforces inward dependency flow with Ports and Adapters to keep the Domain independent from databases and frameworks.
• DDD-ready modeling: Guides Entities, Value Objects, and thin application/use-case orchestration to prevent business logic leakage.
• Operationally guarded architecture: Requires a maker-checker loop focused on security vulnerabilities and operational cost thresholds, plus testable invariants for graceful failure states.
• Diagram-first output: Produces a D2 (or Mermaid fallback) context map that makes ports, adapters, and bounded contexts explicit.

Quick Start

Ask: "Design the architecture for a new payments sub-system, including bounded contexts, port/adaptor boundaries, and diagram-first context mapping with security and cost checks."