Architecture Decision

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.

191 stars 24 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jwynia/agent-skills --skill architecture-decision
Manual install
git clone --depth 1 https://github.com/jwynia/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/tech/development/architecture/architecture-decision ~/.claude/skills/architecture-decision

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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
Read the full skill on GitHub

Details

Skill name
architecture-decision
Path
skills/tech/development/architecture/architecture-decision/SKILL.md
Repo updated
24 February 2026

FAQ

What does the Architecture Decision skill do?

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.

How do I install the Architecture Decision skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jwynia/agent-skills --skill architecture-decision. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Architecture Decision popular?

It lives in jwynia/agent-skills, which has 191 GitHub stars and 24 forks.

Related skills

Abstract Strategy

191

jwynia/agent-skills

Design abstract strategy games with perfect information, no randomness, and strategic depth. Use when designing a board game, exploring abstract strategy games, brainstorming game mechanics, or evaluating game balance. Keywords: board game, game design, strategy, mechanics, balance.

Other24

Adaptation Synthesis

191

jwynia/agent-skills

Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.

Other24

Agent Bootstrap

191

jwynia/agent-skills

Bootstrap agentic development environment from agent.toml manifest

AI, LLMs & Agents24

Ast Grep

228

pproenca/dot-skills

ast-grep rule writing and usage best practices. This skill should be used when writing, reviewing, or debugging ast-grep rules for code search, linting, and transformation. Triggers on tasks involving YAML rules, pattern syntax, meta variables, constraints, or code rewriting.

Software Development19

API Onboarding

88

jonathimer/devmarketing-skills

Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: "API onboarding", "time to first API call", "TTFAC", "developer onboarding", "first API call", "auth simplification", "sandbox environment", "interactive docs", "try it now", "API playground", "developer activation", "onboarding friction

Software DevelopmentIn 1 list

Chrome Extension

228

pproenca/dot-skills

Chrome Extensions (Manifest V3) performance and code quality guidelines. Use when writing, reviewing, or refactoring Chrome extension code including service workers, content scripts, message passing, storage APIs, TypeScript patterns, and testing.

Software Development19

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.