architecture

Document software architecture decisions using ADR templates and design patterns.

1|Updated Jan 12, 2026

Search Tags:#architecture #documentation #scalability #ADR #design-patterns #system-design

Ready to run

npx skills add https://github.com/josavicentevw/ai-agent-skills --skill architecture-josavicentevw

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architecture Skill helps engineers design, evaluate, and document robust software architectures, enabling teams to align decisions with goals, quality attributes, and constraints.

Core Features & Use Cases

System Architecture Design: evaluate and compose monolithic, microservices, serverless, and event-driven architectures with trade-offs.
Architecture Patterns & Documentation: apply C4 models, ADRs, and architectural diagrams; capture decisions and rationale.
Technology Selection & Scalability Planning: compare databases, messaging, and deployment options; plan for performance, reliability, and growth.
Use Case: When tasked with a new platform, rapidly draft architecture options, justify choices, and record decisions for future reference.

Quick Start

Start by gathering requirements, choosing an architectural style, sketching a diagram, and documenting decisions using ADR templates.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document software architecture decisions for scalable systems?▼

You document software architecture decisions by creating Architecture Decision Records (ADRs) that capture choices, trade-offs, and rationale. This skill provides ADR templates and structured design briefs to align decisions with quality attributes and constraints.

What is the best way to choose between microservices and monolithic architecture?▼

Choosing between microservices and monolithic architecture involves evaluating trade-offs for system design. This skill helps compare architectural styles, including serverless and event-driven designs, against your requirements for scalability, performance, and reliability.

How do I structure architecture documentation using the C4 model?▼

Structuring architecture documentation using the C4 model involves applying architectural diagrams and pattern catalogs. This skill supports composing C4 models alongside ADRs to evaluate and document robust software architectures.

Can I use this skill for technology selection and scalability planning?▼

Yes, you can use this skill for technology selection and scalability planning. It enables you to compare databases, messaging options, and deployment strategies while planning for performance, reliability, and future growth.

How do I draft architecture options and justify choices for a new platform?▼

You draft architecture options by gathering requirements, selecting an architectural style, and sketching diagrams. This skill enables rapid composition of design options and justifies choices using structured design briefs and decision records.

When should I not use a microservices architecture for my software design?▼

You should evaluate constraints and trade-offs before adopting microservices architecture. This skill helps document architectural limitations and precautions, ensuring you choose monolithic or event-driven designs only when justified by system requirements.