Architecture Designer Pro

Problem It Addresses

For new systems, technology selection, module decomposition, and database design, the risk is often not missing frameworks but skipping requirements analysis, copying old architectures, or choosing a stack because of familiarity. This can cause rework, performance debt, and communication cost. architecture-designer-pro treats requirements and constraints as mandatory inputs before architecture decisions, rather than optional ceremony.

How It Works

The skill follows a staged process:
- Requirements analysis: identify business goals, functional requirements, non-functional requirements, and constraints such as budget, team expertise, and existing systems.
- Pattern evaluation: compare Monolithic, Microservices, Serverless, and Event-Driven options with trade-offs.
- Module design: define boundaries, interfaces, dependencies, and communication patterns to support parallel development and later refactoring.
- Tech stack selection: evaluate candidates against functional, performance, scalability, ecosystem, and learning-cost criteria.
- Database design: cover entity relationships, indexes, query patterns, migration, and scaling.

It also includes a rationalization checklist that keeps a minimum design record in prototype or time-pressure scenarios, such as an architecture diagram, key decisions, module boundaries, and assumptions.

Boundaries

Best for new system start, refactoring, migration, technology selection, and database modeling. It focuses on process discipline and decision records rather than replacing language tooling, cloud vendor guidance, or domain expertise; for small projects, keep documentation scoped to requirements, boundaries, and key trade-offs.