System Design
Generate comprehensive Technical Architecture Documents with modular design for startups.
Design Principles
- •Modularity: Separated concerns for independent testing and development
- •Simplicity: Minimal complexity appropriate for startup resources
- •Scalability: Designed to grow with user base
- •Cost-effectiveness: Optimized for startup budget
Input
Project folder path in $ARGUMENTS containing:
- •
prd.md- Product requirements (required) - •
idea.md,validate.md- Additional context (optional)
Workflow
Phase 1: Setup & Validation
- •Verify
prd.mdexists - •Read supporting docs if present
- •Read references/tech-stack.md for technology recommendations
- •Backup existing
tad.mdif present
Phase 2: Extract Context
From PRD extract:
- •Product name and vision
- •Core features and requirements
- •User flows
- •Non-functional requirements
- •Third-party integrations
- •Analytics requirements
Phase 3: Clarify Architecture
Ask user (if not clear):
| Decision | Options |
|---|---|
| Deployment | Vercel/Netlify (recommended), AWS, GCP, Self-hosted |
| Database | PostgreSQL, MongoDB, Supabase/Firebase, Multiple |
| Auth | Social (OAuth), Email/password, Magic links, Enterprise SSO |
| Budget | Free tier, <$50/mo, <$200/mo, Flexible |
Phase 4: Research & Validation
Conduct 5 research rounds:
- •Technology Stack: Validate choices against industry standards
- •Infrastructure: Compare hosting for cost and scalability
- •Security: Review OWASP guidelines for chosen stack
- •Risk Assessment: Identify bottlenecks, vendor lock-in
- •Holistic Review: Ensure PRD alignment and startup feasibility
Phase 5: Generate TAD
Create tad.md with sections:
- •System Overview - Purpose, scope, PRD alignment
- •Architecture Diagram - Mermaid diagrams for system and flows
- •Technology Stack - Frontend, backend, database, infrastructure, DevOps
- •System Components - Modular design with interfaces and dependencies
- •Data Architecture - Schema, models, flows, storage
- •Infrastructure - Hosting, environments, scaling, CI/CD, monitoring
- •Security - Auth, authorization, data protection, API security
- •Performance - Targets, optimization strategies, caching
- •Development - Environment setup, project structure, testing, deployment
- •Risks - Risk matrix with mitigations
- •Appendix - Research insights, alternatives, costs, glossary
See references/tad-template.md for full template structure.
Phase 6: Output
- •Write
tad.mdto project folder - •Summarize architecture decisions
- •Highlight modular design benefits
- •List cost estimates by phase
- •Suggest next steps (setup dev environment, create tasks)
Modification Mode
For existing TAD changes:
- •Create timestamped backup
- •Ask what to modify (stack, infrastructure, security, data, scaling)
- •Apply changes preserving structure
- •Update revision history
Guidelines
- •Practical: Implementable solutions for startups
- •Cost-conscious: Consider budget implications
- •Modular: Emphasize separation of concerns
- •Specific: Concrete technology choices
- •Visual: Include mermaid diagrams