architecture▌
sickn33/antigravity-awesome-skills · updated Apr 8, 2026
Structured framework for analyzing requirements, evaluating trade-offs, and documenting architectural decisions.
- ›Provides context discovery questions and project classification to align architecture with actual requirements
- ›Includes trade-off analysis templates and ADR (Architecture Decision Record) documentation patterns for capturing decision rationale
- ›Offers decision trees and anti-pattern guidance to help select appropriate architectural patterns
- ›Emphasizes simplicity-first ap
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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★61 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
architecture has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Chen· Dec 20, 2024
architecture has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kaira Abbas· Dec 12, 2024
Keeps context tight: architecture is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chinedu Agarwal· Dec 12, 2024
architecture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Rao· Dec 8, 2024
I recommend architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Pratham Ware· Dec 4, 2024
architecture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Emma Rao· Nov 27, 2024
Keeps context tight: architecture is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Oshnikdeep· Nov 19, 2024
Solid pick for teams standardizing on skills: architecture is focused, and the summary matches what you get after install.
- ★★★★★Chinedu Jackson· Nov 11, 2024
Solid pick for teams standardizing on skills: architecture is focused, and the summary matches what you get after install.
- ★★★★★Ira Nasser· Nov 3, 2024
I recommend architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 61