system-design-advisor

System design analysis evaluates data-flow, state transitions, and consistency guarantees across planned changes by applying seven lenses including Atomicity, Idempotency, Concurrency, and CAP Theorem to each implementation phase. It outputs a structured markdown report with trade-offs and proposed actions for developer approval before any code is written.

The best way to document architectural patterns and database selection trade-offs is applying the CAP Theorem lens during the pre-coding analysis phase to produce a comprehensive system-design-analysis.md file. This report captures findings, trade-offs, and approved decisions for coder reference.

Planning for resilience and idempotency involves analyzing these properties as dedicated lenses applied to each phase of proposed system changes. The analysis identifies potential design flaws related to state transitions and data-flow, ensuring reliability across distributed systems before implementation begins.

You need to generate a system design analysis report after completing the research phase and before writing any code. This pre-coding analysis prevents design flaws by evaluating atomicity, consistency guarantees, and architectural patterns, producing a markdown document the coder must read.

Yes, the system design analysis supports optional diagrams to illustrate data-flow and state transitions. These visual aids complement the seven-lens analysis and help clarify architecture reviews by visually mapping how data moves and states change across planned implementations.

Yes, the system design analysis operates without external dependencies or components, functioning as a self-contained analytical process. It applies seven architectural lenses to planned changes and generates a standalone markdown report with findings, trade-offs, and proposed actions requiring no additional tools.