architecture

Analyze requirements, evaluate trade-offs, and document Architecture Decision Records.

1|Updated Sep 25, 2025

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

Ready to run

npx skills add https://github.com/arroschaves/brandaocontador-site --skill architecture-arroschaves

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/arroschaves/brandaocontador-site/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/arroschaves/brandaocontador-site --skill architecture-arroschaves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, ensuring that system designs are well-reasoned, documented, and aligned with project requirements and constraints.

Core Features & Use Cases

Requirements Analysis: Guides the process of understanding project needs and constraints.
Trade-off Evaluation: Facilitates the comparison of different architectural options.
ADR Documentation: Provides templates and guidance for documenting Architecture Decisions.
Pattern Selection: Offers decision trees and references for choosing appropriate architectural patterns.
Use Case: When starting a new project, use this Skill to analyze requirements, evaluate options like microservices vs. monolith, and document the final decision using an Architecture Decision Record (ADR).

Quick Start

Use the architecture skill to analyze requirements for a new SaaS product.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architectural decisions for a new software project?▼

You can document architectural decisions using Architecture Decision Records (ADRs). This Skill provides markdown templates and guidance to generate ADRs, ensuring you store them in a structured docs/architecture directory for future reference.

What is the best way to evaluate system design trade-offs like microservices vs monolith?▼

Evaluating system design trade-offs requires comparing architectural options against project requirements. This framework facilitates trade-off evaluation by analyzing constraints like project scale, team expertise, and timeline to guide your pattern selection.

How do I choose the right architectural patterns based on my team's expertise?▼

Choosing architectural patterns involves analyzing requirements and constraints like team expertise and timeline. This framework offers decision trees and references to match your project scale with appropriate system design patterns.

When do I need to create an Architecture Decision Record?▼

You need an Architecture Decision Record (ADR) when making significant architectural choices for a new project. Creating ADRs ensures your system designs are well-reasoned, properly documented, and aligned with project requirements.

Does this architecture framework support requirements analysis for SaaS products?▼

Yes, this architecture framework supports requirements analysis for SaaS products. It guides the process of understanding project needs and constraints to ensure your system design aligns with specific software requirements.