architecture

Analyzes software requirements and constraints to recommend architecture with trade-offs and ADRs.

1|Updated May 6, 2026

Search Tags:#architecture #software engineering #system design #design patterns #adr #trade-offs

Ready to run

npx skills add https://github.com/ag47-pt/Website --skill architecture-ag47-pt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ag47-pt/Website/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/ag47-pt/Website --skill architecture-ag47-pt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams make structured software architecture decisions by analyzing requirements, constraints, trade-offs, and long-term consequences instead of relying on intuition alone.

Core Features & Use Cases

Requirements Analysis: Guides discovery of scale, team, timeline, domain, and technical constraints before selecting an architecture.
Trade-off Evaluation: Helps compare architectural options, document decisions with ADRs, and avoid unnecessary complexity.
Pattern Selection: Provides decision frameworks for choosing appropriate patterns such as modular monoliths, microservices, DDD, APIs, and data access strategies.

Quick Start

Use the architecture skill to analyze my application requirements and recommend an architecture with trade-offs and an ADR.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I evaluate software architecture trade-offs before choosing a pattern?▼

To evaluate architecture trade-offs, analyze your application's specific requirements, constraints, and long-term consequences using a structured decision framework to compare options and avoid unnecessary complexity.

What is the best way to document architecture decisions for my team?▼

The best way to document architecture decisions is by creating an Architecture Decision Record (ADR) that captures the selected patterns, evaluated trade-offs, and the rationale behind balancing complexity with project needs.

How do I choose between a modular monolith and microservices for system design?▼

Choosing between a modular monolith and microservices requires analyzing your system's scale, team structure, timeline, and domain constraints, then applying a decision framework to select the appropriate architectural pattern.

What requirements should I analyze before selecting a software architecture?▼

Before selecting a software architecture, you should analyze your application's scale, team size, timeline, domain complexity, and technical constraints to ensure the design fits your specific context.

When should I avoid unnecessary complexity in architectural pattern selection?▼

You should avoid unnecessary complexity during architectural pattern selection when your project needs can be met by a simpler design, preventing over-engineering by carefully balancing complexity against actual requirements.

Can I use Domain-Driven Design (DDD) patterns for my application structure?▼

You can use Domain-Driven Design (DDD) patterns for your application structure by evaluating your domain complexity and technical constraints through a decision framework to determine if they suit your system design needs.