architecture

Name: architecture
Availability: InStock
Author: martialarcon

Analyze requirements and document architectural decisions with Architecture Decision Records.

1|Updated Feb 15, 2026

Search Tags:#architecture #decision making #system design #patterns #ADR #trade-offs

Ready to run

npx skills add https://github.com/martialarcon/claude-code-expert --skill architecture-martialarcon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/martialarcon/claude-code-expert/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/martialarcon/claude-code-expert --skill architecture-martialarcon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, evaluating trade-offs, and documenting the rationale behind system design choices.

Core Features & Use Cases

Requirements Analysis: Guides the process of understanding project needs, scale, team dynamics, and constraints.
Trade-off Evaluation: Offers a systematic way to compare different architectural options and their implications.
ADR Documentation: Facilitates the creation of Architecture Decision Records to capture and communicate key decisions.
Use Case: When designing a new microservice, use this Skill to analyze requirements, compare options like REST vs. GraphQL for the API, and document the final decision and its trade-offs in an ADR.

Quick Start

Use the architecture skill to analyze requirements for a new project and suggest initial architectural patterns.

Frequently Asked Questions about architecture

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

FAQPage Schema

What is an Architecture Decision Record and how does it help with system design?▼

An Architecture Decision Record (ADR) is a structured document that captures the rationale behind system design choices, helping teams communicate and evaluate trade-offs during architectural decision-making. It ensures the context and implications of patterns are preserved for future reference.

How do I evaluate architectural trade-offs when choosing API patterns for a new microservice?▼

To evaluate architectural trade-offs for a microservice, analyze project requirements, team dynamics, and scale to compare options like REST versus GraphQL. This systematic comparison reveals the implications of each pattern, guiding the selection process and documenting the final decision in an ADR.

Can I use this framework to analyze requirements for complex system design?▼

Yes, this framework guides requirements analysis for complex system design by assessing project needs, scale, and constraints. It helps translate these factors into actionable architectural patterns suitable for your specific team dynamics and complexity levels.

What is the best way to document architectural patterns and their trade-offs?▼

The best way to document architectural patterns and their trade-offs is by creating Architecture Decision Records. ADRs provide a standardized format to record the selected system design, the evaluated alternatives, and the rationale behind the final architectural decision-making process.

When should I not use a specific architectural pattern for my project scale?▼

You should reconsider an architectural pattern when project requirements, scale, or team dynamics exceed its intended complexity threshold. The framework helps identify these limitations by evaluating trade-offs, ensuring you avoid patterns that introduce unnecessary overhead or constraints for your specific context.