tech-stack-architect

Tech stack architecture design starts with your PROJECT-OVERVIEW.md, then systematically selects frontend, backend, database, and DevOps technologies. The process generates TECH-STACK.md with category tables and integration trade-offs, plus ARCHITECTURE.md with data flows, mermaid diagrams, and scalability strategy to document your complete system design.

Architecture documentation covers component details, data flows visualized with mermaid diagrams, deployment topology, scalability strategy, and security architecture. It translates technology choices into concrete system behavior, showing how frontend, backend, database, and infrastructure components interact and scale.

Use full architecture design when starting new projects, re-architecting existing systems, or evaluating major technology shifts. Simple technology selection alone misses data flows, integration points, scalability constraints, and security implications that architecture design captures through documentation and diagrams.

Yes, architecture design generates mermaid diagrams showing data flows and deployment topology automatically from your requirements. This creates visual, version-controlled documentation of how system components connect and communicate across your tech stack.

Document trade-offs between competing technologies in each category: performance vs. complexity, cost vs. capability, learning curve vs. team familiarity, and operational overhead. TECH-STACK.md captures these trade-offs alongside migration paths and team considerations for informed technology decisions.

Architecture design includes explicit scalability strategy covering load distribution, database scaling patterns, caching layers, and infrastructure elasticity. Documenting these patterns upfront prevents re-architecture later and aligns technology choices with growth projections from your project requirements.