sickn33

architecture

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

sickn33 45,418 6,654 Updated 7mo ago

Resources

5
GitHub

Install

npx skillscat add sickn33/antigravity-awesome-skills/architecture

Install via the SkillsCat registry.

About this skill

We need to produce a 2-3 sentence plain-text summary, objective, factual, no marketing, no superlatives, no calls to action, natural prose, no bullet points, no headings, no markdown. At most 60 words. Must be only the summary text. We need to describe what the skill does: provides an architectural decision-making framework, includes requirements analysis, trade-off evaluation, ADR documentation. Solves problem: helps make architecture decisions, analyze system design, ensure rationale captured, avoid unnecessary complexity.

SKILL.md

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