skills.rest
capaas2
capaas2COMMUNITY
Explore all skills by this author →
GitHub

architecture

Analyze software architecture requirements and recommend design choices with trade-offs.

Updated Apr 4, 2026
Search Tags:#architecture#system design#adr#requirements analysis#trade-offs#pattern selection
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill architecture-capaas2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/capaas2/Site-teste --skill architecture-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you choose the right software architecture by clarifying requirements, evaluating trade-offs, and documenting decisions so you avoid over-engineering and costly redesigns.

Core Features & Use Cases

  • Requirements discovery: Ask the right questions about scale, team size, timeline, domain complexity, and constraints before proposing an architecture.
  • Pattern selection: Choose among monolith, modular monolith, microservices, event-driven, DDD, repository, and other patterns based on real project needs.
  • Trade-off analysis: Compare options, capture rationale in ADRs, and define when to revisit decisions.
  • Use case: You are starting a new product and need to determine whether a simple modular monolith is enough or whether a more distributed design is justified.

Quick Start

Ask the architecture skill to assess your project requirements and recommend an architecture with clear trade-offs.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I choose the right software architecture pattern for my project?▼

Software architecture pattern selection requires analyzing scale, team size, timeline, and domain complexity. This Skill evaluates those project requirements to recommend appropriate designs like modular monolith or microservices while avoiding over-engineering.

What is the best way to document system design trade-offs and decisions?▼

Documenting system design trade-offs is best achieved through Architecture Decision Records (ADRs). This Skill compares architectural options, captures the rationale for each decision, and defines exactly when to revisit those choices.

Do I need microservices for my SaaS MVP or is a monolith enough?▼

Whether you need microservices for a SaaS MVP depends on your specific scale and team constraints. This Skill validates architectural complexity against your timeline and team size to determine if a simple monolith is sufficient.

How does trade-off analysis prevent over-engineering in system design?▼

Trade-off analysis prevents over-engineering by validating architectural complexity against real project constraints. This Skill assesses your requirements to ensure distributed designs or domain-driven patterns are only recommended when justified by actual scale.

When should I use domain-driven design over a modular monolith architecture?▼

You should use domain-driven design over a modular monolith architecture when high domain complexity justifies the added structure. This Skill evaluates your specific requirements to recommend the correct pattern and prevent costly redesigns.

Related Skills

Explore More Software Engineering Skills→
VoTruongDanhVoTruongDanh

architecture

architecture for your project.

Community
Advanced
cy-walicy-wali

architecture

Generate Architecture Decision Records documenting technology decisions with trade-offs.

Community
Advanced
ag47-ptag47-pt
1

architecture

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

Community
Intermediate
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic