architecture-design

System architecture decisions between monolith and microservices are evaluated by assessing product scale, domain module boundaries, and capacity constraints to determine the optimal pattern. The skill highlights architectural issues and recommends the appropriate layering structure for your context.

Architecture Decision Records (ADRs) provide traceability by capturing system architecture choices with clear ownership and versioning. This skill generates ADR drafts alongside Mermaid or PlantUML diagrams to document infrastructure topology and data model rationale.

API contracts and data models are defined by establishing entity ownership, endpoints, request and response schemas, and versioning rules. This skill evaluates your modular monolith boundaries to produce explicit API specifications and structured data modeling guidelines.

System architecture diagrams can be generated automatically using Mermaid or PlantUML syntax to visualize infrastructure topology and module dependencies. This skill produces diagrams directly from your architecture assessment to illustrate layering patterns and data flows.

Architecture design for early-stage startup products is supported by evaluating initial capacity planning, risk evaluation, and infrastructure topology choices. It satisfies startup requirements for architecture assessment and system design without enforcing premature microservices complexity.