skills.rest
GainInsightDev
GainInsightDevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

af-decide-architecture

Create and manage Architecture Decision Records with templates and an index.

Updated Feb 8, 2026
Search Tags:#architecture#code review#decision making#documentation#adr#patterns
One-click install
npx skills add https://github.com/GainInsightDev/websites --skill af-decide-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: af-decide-architecture
Source: https://github.com/GainInsightDev/websites/tree/main/.claude/skills/af-decide-architecture
Command: npx skills add https://github.com/GainInsightDev/websites --skill af-decide-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams make, document, and adhere to architectural decisions, preventing architectural drift and ensuring consistency across projects.

Core Features & Use Cases

  • ADR Creation & Management: Guides the creation of Architecture Decision Records (ADRs) for significant choices.
  • Architectural Compliance: Reviews code and changes against existing ADRs to ensure alignment.
  • Use Case: When introducing a new database technology, this Skill will guide you through creating an ADR, documenting the trade-offs considered, and ensuring the implementation aligns with the accepted decision.

Quick Start

Use the af-decide-architecture skill to create a new ADR for a proposed change to the authentication system.

Frequently Asked Questions about af-decide-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural decisions to prevent drift across projects?▼

You can document architectural decisions by creating Architecture Decision Records (ADRs) that capture context, trade-offs, and conclusions. This prevents architectural drift by ensuring teams reference a consistent decision index during implementation.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents a significant architectural choice, its context, and consequences. You need an ADR when introducing new technologies or patterns to ensure consistency across projects.

How do I review code for architectural compliance against existing decisions?▼

You review code for architectural compliance by evaluating changes against documented ADRs. This ensures the implementation aligns with the accepted architectural decisions and patterns established for the project.

What's the best way to manage multiple Architecture Decision Records?▼

The best way to manage multiple Architecture Decision Records is using an ADR index alongside structured templates. This approach facilitates efficient creation, documentation, and enforcement of architectural patterns across your codebase.

When should I not use an ADR for code changes?▼

You should not use an ADR for routine code changes that lack significant architectural impact. ADRs are intended for major decisions like introducing new database technologies or evaluating architecture patterns, not minor refactoring.

Related Skills

Explore More Software Engineering Skills→
brabos-aibrabos-ai
8

add-architecture-discovery

Analyze project codebases to generate technical specs and architecture contracts in CLAUDE.md.

Official
Advanced
Euraika-LabsEuraika-Labs
14

code-review

Review source files for architecture, SOLID, ADR, and performance compliance.

Official
Advanced
phoenicisfphoenicisf

architecture

Document architectural decisions using ADR templates with context and trade-offs.

Community
Advanced
im9im9
1

adr

Generate ADR documents with context, alternatives, and trade-offs.

Community
Intermediate