Skip to content
Skillpedia
General coding48k · #2198

architecture

Lets your agent assist with architecture decision-making. It analyzes requirements, evaluates options, and documents the choices made.

What it does

This tool helps make important decisions about how to build software. It analyzes requirements, compares options, and documents the choices made.

When to use it

  • ✓When starting a new software project.
  • ✓When needing to choose which technology to use.
  • ✓When documenting architecture decisions.

Example of what to ask your AI

“How should I structure the architecture for an e-commerce application?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/architecture/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/architecture/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool reads documents explaining how to analyze requirements, compare options, and record decisions. It focuses on starting simple and adding complexity only when needed.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill architecture

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/architecture/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
FAQ

What is an ADR?

ADR stands for Architecture Decision Record. It's a document explaining why a specific architecture decision was made.

Why start with simplicity?

Starting simple makes the system easier to understand and modify. Adding complexity only when truly necessary avoids unnecessary problems.

What are the limitations of this tool?

It doesn't replace testing or expert review. Use it only for tasks that clearly fit its purpose and ask for clarification if something is unclear.

Details

Original description by the author

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

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2198
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills