architecture-selection

Guide engineers in selecting architecture patterns for scalable systems.

Updated Dec 28, 2025

Search Tags:#architecture #serverless #microservices #patterns #monolith #event-driven #C4

Ready to run

npx skills add https://github.com/I2olanD/dotfiles --skill architecture-selection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-selection
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/architecture-selection
Command: npx skills add https://github.com/I2olanD/dotfiles --skill architecture-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers to choose architecture patterns for scalable systems.

Core Features & Use Cases

Comprehensive pattern coverage: Monolith, Microservices, Event-Driven, and Serverless with clear C4 context.
Decision documentation: ADR-style decisions, rationale, and trade-offs to align stakeholders.
Quick-start design sessions: generate a decision-ready architecture outline for a given system and requirements.

Quick Start

Invoke architecture-pattern-selection to compare monolith, microservices, event-driven, and serverless patterns for a given system and generate a decision guide.

Frequently Asked Questions about architecture-selection

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

FAQPage Schema

How do I choose between monolith, microservices, event-driven, and serverless architecture patterns?▼

To choose an architecture pattern, compare monolith, microservices, event-driven, and serverless options against your system requirements. This involves evaluating scalability considerations and documenting trade-offs to generate a decision-ready architecture outline.

What is the best way to document architecture trade-offs for stakeholders?▼

The best way to document architecture trade-offs is by generating ADR-style decision records. This captures the rationale and comparisons between monolith, microservices, and serverless patterns to align stakeholders on the chosen architecture.

How does C4 modeling work for serverless and event-driven systems?▼

C4 modeling works for serverless and event-driven systems by providing a clear context view of the architecture. It maps out the structural relationships and scalability considerations needed to visualize how the chosen pattern handles system requirements.

When do I need to generate an architecture decision record for a scalable system?▼

You need to generate an architecture decision record during design reviews when selecting patterns for scalable systems. It documents the rationale and trade-offs of monolith, microservices, or serverless choices to align stakeholders before implementation.

Can I compare microservices and monolith patterns for a given system's scalability requirements?▼

Yes, you can compare microservices and monolith patterns for a given system. The process evaluates scalability considerations across microservices, monolith, event-driven, and serverless architectures to produce a decision guide tailored to your requirements.