Agent skill

Architecture Decision

by jwynia in jwynia/agent-skills

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns.

MITAuto-check passedDevelopment

Install Architecture Decision

skills CLI
$ npx skills add jwynia/agent-skills --skill architecture-decision -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills architecture-decision --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tech/development/architecture/architecture-decision .claude/skills/architecture-decision && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architecture-decision
GitHub stars
170
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
498 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns.

  • Works in 4 steps: Create abstraction over current… → Implement new solution behind abstraction → Switch to new implementation → …
  • Asks about architecture decision
  • SKILL.md covers When to Use This Skill, Core Principle, The Trade-off Triangle and Quality Attributes, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architecture Decision is an agent skill from jwynia/agent-skills. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Works with any project. Integrates with system-design for ADR templates.

It sits in Development, covering Architecture decision records, Technical debt and Design patterns. The licence is MIT.

When your agent uses it

  • Asks about architecture decision
  • Design pattern selection
  • Technology choice
  • Needs to evaluate architectural trade-offs

Example prompts

  • “architecture decision”
  • “design pattern selection”
  • “technology choice”
  • “/architecture-decision”

Requirements

  • Compatibility (from SKILL.md): Works with any project. Integrates with system-design for ADR templates.

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Works with any project. Integrates with system-design for ADR templates.

    From compatibility in the SKILL.md frontmatter.

Context cost

Architecture Decision loads about 1.5k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 498 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 498 words, ~1,465 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-decision/SKILL.md (or your agent's skills folder).
name
architecture-decision
description
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.
compatibility
Works with any project. Integrates with system-design for ADR templates.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
diagnostic
metadata.mode
diagnostic+evaluative
metadata.domain
agile-software

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:

VertexMaximized ByCost
SimplicityMonolith, sync communication, single DBScalability limits
FlexibilityMicroservices, event-driven, pluginsComplexity overhead
PerformanceCaching, denormalization, optimized codeMaintainability

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
ContextPreferred PatternsAvoid
Small teamMonolith, vertical slices, shared DBMicroservices, complex abstractions
Multiple teamsService boundaries, API contractsShared state, tight coupling
Scale Context
ContextPreferred PatternsReasoning
StartupMonolith first, vertical scalingOptimize for development speed
EnterpriseService mesh, horizontal scalingOptimize for operational scale

Decision Matrix Template

OptionConsistencyFlexibilityScalabilityComplexityCostTotal
Option A5232315
Option B3543318
Option C2351213

Weight factors based on context priorities.

Architecture Decision Record (ADR) Template

markdown
# 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]
Show full SKILL.md (200 more words)Show less

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
TypeExamplesPayment Strategy
DesignMissing abstractions, tight couplingRefactoring sprints
CodeDuplication, complexity, poor namingContinuous cleanup
TestMissing tests, flaky testsTest improvement
DocumentationMissing docs, outdated diagramsDocumentation 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

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

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/tech/development/architecture/architecture-decision of jwynia/agent-skills.

Open the folder on GitHubat commit e02ec7e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jwynia/agent-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Architecture Decision next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architecture Decision compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Decision this skilljwynia/agent-skills1701 repos~1.5kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Architecture DesignerAratKruglik/claude-laravel1551 repos~895Automated safety check: PassNone
Cto Advisoralirezarezvani/claude-skills28k1 repos~3kAutomated safety check: PassMIT
Architecture Optimizationwondelai/skills2.4k—~7.4kAutomated safety check: PassMIT
Design Code Architecturewondelai/skills2.4k—~6.7kAutomated safety check: PassMIT

Similar skills

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Architecture Designer

    AratKruglik/claude-laravel

    A skill your agent uses when designing new system architecture, reviewing existing designs, or making architectural decisions.

    155 GitHub starsUsed in 1 repo~895 tokens
    DevelopmentAuto-check passed
  • Cto Advisor

    alirezarezvani/claude-skills

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    28k GitHub starsUsed in 1 repo~3k tokens
    DevelopmentAuto-check passed
  • Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable.

    2.4k GitHub stars~7.4k tokensUpdated 29 days ago
    DevelopmentAuto-check passed
  • Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest.

    2.4k GitHub stars~6.7k tokensUpdated 29 days ago
    DevelopmentAuto-check passed
  • Improve Code Quality

    wondelai/skills

    Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale.

    2.4k GitHub stars~6.2k tokensUpdated 29 days ago
    DevelopmentAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Architecture Decision

What does Architecture Decision do?

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. Architecture Decision is an agent skill from jwynia/agent-skills. Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns.

When should I use Architecture Decision?

Architecture Decision fits situations like: asks about architecture decision; design pattern selection; technology choice; needs to evaluate architectural trade-offs.

How do I install Architecture Decision in Claude Code?

Run `npx skills add jwynia/agent-skills --skill architecture-decision -a claude-code`. Or copy the skill folder (skills/tech/development/architecture/architecture-decision in jwynia/agent-skills) into .claude/skills/architecture-decision in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Decision in Codex?

Run `npx skills add jwynia/agent-skills --skill architecture-decision -a codex`. Or copy the skill folder (skills/tech/development/architecture/architecture-decision in jwynia/agent-skills) into .agents/skills/architecture-decision in your project. Codex loads it when a task matches its description.

Can I use Architecture Decision in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill architecture-decision -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-decision, .gemini/skills/architecture-decision, .github/skills/architecture-decision and .opencode/skills/architecture-decision in your project.

What does Architecture Decision need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Decision is instructions for the agent only. Compatibility (from SKILL.md): Works with any project. Integrates with system-design for ADR templates..

Does Architecture Decision access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architecture Decision safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architecture Decision use?

Architecture Decision is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architecture Decision use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architecture Decision?

Skills that share tags, products or a category with Architecture Decision: Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Designer (AratKruglik/claude-laravel, 155 stars), Cto Advisor (alirezarezvani/claude-skills, 28k stars) and Architecture Optimization (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Decision?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.