Index of every page on this site: llms.txt
All skills
jwynia avatar

/architecture-decision

@e02ec7e
by J Wyniajwynia/agent-skills191 stars
24
Run it yourself

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.

Use this Skill: https://skilld.dev/gh/jwynia/agent-skills/architecture-decision

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈102 tokens for metadata: the name and description. ≈1.3k when used: this file.

Description uses 5.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈408 characters, or 5.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Architecture Decision

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns for context. Provides frameworks for pattern selection, ADR creation, and technical debt management.

When to Use This Skill

Use this skill when:

  • Making technology choices
  • Evaluating architectural patterns
  • Creating Architecture Decision Records
  • Assessing technical debt
  • Comparing design alternatives

Do NOT use this skill when:

  • Writing implementation code
  • Working on requirements (use requirements-analysis)
  • Doing full system design (use system-design)

Core Principle

Context drives decisions. No pattern is universally good or bad. The best architecture is not the most elegant—it's the one that best serves its purpose while remaining maintainable and evolvable.

The Trade-off Triangle

Every architectural decision involves trade-offs:

Vertex Maximized By Cost
Simplicity Monolith, sync communication, single DB Scalability limits
Flexibility Microservices, event-driven, plugins Complexity overhead
Performance Caching, denormalization, optimized code Maintainability

Balance Strategies:

  • Start simple, add complexity as needed
  • Measure before optimizing
  • Use abstractions to defer decisions
  • Evolve incrementally

Quality Attributes

Performance

  • Metrics: Response time (p50, p95, p99), throughput, resource utilization
  • Tactics: Caching, load balancing, async processing

Scalability

  • Dimensions: Horizontal, vertical, elastic
  • Patterns: Stateless services, sharding, event streaming

Reliability

  • Metrics: Uptime, MTBF, MTTR
  • Patterns: Circuit breakers, retries, redundancy

Maintainability

  • Factors: Readability, modularity, testability
  • Patterns: Clean architecture, DDD, SOLID

Context-Pattern Mapping

Team Context

Context Preferred Patterns Avoid
Small team Monolith, vertical slices, shared DB Microservices, complex abstractions
Multiple teams Service boundaries, API contracts Shared state, tight coupling

Scale Context

Context Preferred Patterns Reasoning
Startup Monolith first, vertical scaling Optimize for development speed
Enterprise Service mesh, horizontal scaling Optimize for operational scale

Decision Matrix Template

Option Consistency Flexibility Scalability Complexity Cost Total
Option A 5 2 3 2 3 15
Option B 3 5 4 3 3 18
Option C 2 3 5 1 2 13

Weight factors based on context priorities.

Architecture Decision Record (ADR) Template

# ADR-[NUMBER]: [TITLE]

## Status
[Proposed | Accepted | Deprecated | Superseded]

## Context
[What is the situation requiring a decision?]

### Requirements
- [Requirement 1]
- [Requirement 2]

### Constraints
- [Constraint 1]
- [Constraint 2]

## Decision
[What is the decision?]

### Justification
- [Reason 1]
- [Reason 2]

## Consequences

### Positive
- [Benefit 1]
- [Benefit 2]

### Negative
- [Drawback 1]
- [Drawback 2]

## Alternatives Considered

### [Alternative 1]
Reason rejected: [Why]

### [Alternative 2]
Reason rejected: [Why]

Architectural Refactoring Patterns

Branch by Abstraction

  1. Create abstraction over current implementation
  2. Implement new solution behind abstraction
  3. Switch to new implementation
  4. Remove old implementation

Strangler Fig

  1. Identify boundary
  2. Implement new solution for new features
  3. Gradually migrate old features
  4. Retire old system

Parallel Run

  1. Implement new solution
  2. Run both old and new
  3. Compare results
  4. Switch when confident

Technical Debt Management

Debt Categories

Type Examples Payment Strategy
Design Missing abstractions, tight coupling Refactoring sprints
Code Duplication, complexity, poor naming Continuous cleanup
Test Missing tests, flaky tests Test improvement
Documentation Missing docs, outdated diagrams Documentation sprints

Metrics

  • Debt ratio: Debt work / Total work (target < 20%)
  • Interest rate: Extra effort due to debt
  • Debt ceiling: Maximum acceptable debt

Anti-Patterns

Big Ball of Mud

Symptoms: No clear structure, everything depends on everything Remedy: Identify boundaries, extract modules, establish interfaces

Distributed Monolith

Symptoms: Services must deploy together, sync chains, shared DBs Remedy: Merge related services, async communication, separate DBs

Golden Hammer

Symptoms: One solution for all problems, force-fitting patterns Remedy: Learn alternatives, evaluate objectively, prototype options

Related Skills

  • system-design - Full system design with ADRs
  • code-review - Implementation validation
  • task-decomposition - Breaking down architectural work
  • requirements-analysis - Understanding constraints

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides architectural guidelines and templates for software design decisions. It contains no executable code, external dependencies, or network operations, and it does not exhibit any malicious patterns.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e02ec7e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago
compatibility
Works with any project. Integrates with system-design for ADR templates.
Other metadata
metadata
{
  "author": "jwynia",
  "version": "1.0",
  "type": "diagnostic",
  "mode": "diagnostic+evaluative",
  "domain": "agile-software"
}

README badge

README badge for jwynia/agent-skills/architecture-decision