What problem does it solve?
After technical research is complete, teams often struggle to translate findings into a concrete system architecture. This Skill provides a structured methodology for choosing architecture patterns, designing system layers, and defining project directory structures so the architecture document is consistent and grounded in framework conventions.
Core Features & Use Cases
- Architecture Pattern Selection: Decision trees and comparison tables for choosing between monolith, frontend-backend separation, microservices, and serverless based on project scale and team size.
- System Layering & Diagrams: Templates for layered architecture and Mermaid-based system architecture diagrams covering clients, gateways, services, and data layers.
- Directory Structure Templates: Ready-made project structures for Next.js App Router, Express + React, Python FastAPI, and Go, plus a tech stack overview table format.
- Use Case: After completing technology research for a new web product, the architect agent uses this methodology to produce the architecture overview and directory structure chapters of the architecture document.
Quick Start
Ask the architect agent to design the system architecture for your project based on the completed technology research, including pattern selection, an architecture diagram, and a directory structure.
