Architecture

by davila78da17d671b6fNo license32K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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

AI-generated overview

Framework for making software architecture decisions: requirements analysis, trade-off evaluation, pattern selection, and ADR documentation.

What it does
Guides an agent through architectural decision-making by pointing to reference files on context discovery, trade-off analysis, pattern selection, and worked examples. It helps analyze requirements and constraints, compare design patterns and anti-patterns, and record the rationale for significant decisions as ADRs. A validation checklist confirms requirements, constraints, trade-offs, simpler alternatives, and team expertise before finalizing an architecture.
When to use it
Use when starting an architecture design, choosing between system design patterns, or documenting the reasoning behind a significant technical decision. Also useful for reviewing an existing system design against simpler alternatives.
Requirements
No scripts; instructions only. The agent needs file-reading tools (Read, Glob, Grep) to load the referenced markdown files. No packages, credentials, or network access are required.

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.

FileDescriptionWhen to Read
context-discovery.mdQuestions to ask, project classificationStarting architecture design
trade-off-analysis.mdADR templates, trade-off frameworkDocumenting decisions
pattern-selection.mdDecision trees, anti-patternsChoosing patterns
examples.mdMVP, SaaS, Enterprise examplesReference implementations
patterns-reference.mdQuick lookup for patternsPattern comparison

🔗 Related Skills

SkillUse 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

Source and attribution

Source:davila7/claude-code-templatesincli-tool/components/skills/development/architectureat commit8da17d6

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal