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

1. Verify prd.md exists
2. Read supporting docs if present
3. Read references/tech-stack.md for technology recommendations
4. Backup existing tad.md if 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):

Phase 4: Research & Validation

Conduct 5 research rounds:

1. Technology Stack: Validate choices against industry standards
2. Infrastructure: Compare hosting for cost and scalability
3. Security: Review OWASP guidelines for chosen stack
4. Risk Assessment: Identify bottlenecks, vendor lock-in
5. Holistic Review: Ensure PRD alignment and startup feasibility

Phase 5: Generate TAD

Create tad.md with sections:

1. System Overview – Purpose, scope, PRD alignment
2. Architecture Diagram – Mermaid diagrams for system and flows
3. Technology Stack – Frontend, backend, database, infrastructure, DevOps
4. System Components – Modular design with interfaces and dependencies
5. Data Architecture – Schema, models, flows, storage
6. Infrastructure – Hosting, environments, scaling, CI/CD, monitoring
7. Security – Auth, authorization, data protection, API security
8. Performance – Targets, optimization strategies, caching
9. Development – Environment setup, project structure, testing, deployment
10. Risks – Risk matrix with mitigations
11. Appendix – Research insights, alternatives, costs, glossary

See references/tad-template.md for full template structure.

Phase 6: README Maintenance (ideas repo)

After writing tad.md, if the project folder is inside an ideas repo, update the repo README ideas table:

• Preferred: cd to repo root and run python3 scripts/update_readme_ideas_index.py (if it exists)
• Fallback: update README.md manually (ensure TAD status becomes ✅ for that idea)

Phase 7: Commit and push (mandatory)

• Commit immediately after updates.
• Push immediately to remote.
• If push is rejected: git fetch origin && git rebase origin/main && git push.

Do not ask for additional push permission once this skill is invoked.

Phase 8: Output

1. Write tad.md to project folder
2. Summarize architecture decisions
3. Highlight modular design benefits
4. List cost estimates by phase
5. Suggest next steps (setup dev environment, create tasks)

Reporting with GitHub links (mandatory)

When reporting completion, include:

• GitHub link to tad.md
• GitHub link to README.md when it was updated
• Commit hash

If this project is in the ideas repo, use:

• https://github.com/luongnv89/ideas/blob/main/<relative-path>

Modification Mode

For existing TAD changes:

1. Create timestamped backup
2. Ask what to modify (stack, infrastructure, security, data, scaling)
3. Apply changes preserving structure
4. 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