4e8e5069fa
- Added: api-patterns, app-builder, architecture, bash-linux, behavioral-modes, clean-code, code-review-checklist, database-design, deployment-procedures, docker-expert, documentation-templates, game-development, geo-fundamentals, i18n-localization, lint-and-validate, mobile-design, nestjs-expert, nextjs-best-practices, nodejs-best-practices, parallel-agents, performance-profiling, plan-writing, powershell-windows, prisma-expert, python-patterns, react-patterns, red-team-tactics, seo-fundamentals, server-management, tailwind-patterns, tdd-workflow, typescript-expert, vulnerability-scanner - Updated README: skill count 179 → 223 - Added credit for vudovn/antigravity-kit (MIT License) Source: https://github.com/vudovn/antigravity-kit
56 lines
1.7 KiB
Markdown
56 lines
1.7 KiB
Markdown
---
|
|
name: architecture
|
|
description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
|
|
allowed-tools: Read, Glob, Grep
|
|
---
|
|
|
|
# Architecture Decision Framework
|
|
|
|
> "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
|
|
|
|
## 🎯 Selective Reading Rule
|
|
|
|
**Read ONLY files relevant to the request!** Check the content map, find what you need.
|
|
|
|
| File | Description | When to Read |
|
|
|------|-------------|--------------|
|
|
| `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
|
|
| `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
|
|
| `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
|
|
| `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
|
|
| `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
|
|
|
|
---
|
|
|
|
## 🔗 Related Skills
|
|
|
|
| Skill | Use For |
|
|
|-------|---------|
|
|
| `@[skills/database-design]` | Database schema design |
|
|
| `@[skills/api-patterns]` | API design patterns |
|
|
| `@[skills/deployment-procedures]` | Deployment architecture |
|
|
|
|
---
|
|
|
|
## Core Principle
|
|
|
|
**"Simplicity is the ultimate sophistication."**
|
|
|
|
- Start simple
|
|
- Add complexity ONLY when proven necessary
|
|
- You can always add patterns later
|
|
- Removing complexity is MUCH harder than adding it
|
|
|
|
---
|
|
|
|
## Validation Checklist
|
|
|
|
Before finalizing architecture:
|
|
|
|
- [ ] Requirements clearly understood
|
|
- [ ] Constraints identified
|
|
- [ ] Each decision has trade-off analysis
|
|
- [ ] Simpler alternatives considered
|
|
- [ ] ADRs written for significant decisions
|
|
- [ ] Team expertise matches chosen patterns
|