skills.rest
SSiertsema
SSiertsemaCOMMUNITY
Explore all skills by this author →
GitHub

architecture-pattern-selection

Select architectural patterns with trade-offs and evolution roadmaps.

1|Updated Nov 29, 2025
Search Tags:#architecture#microservices#evolution#monolith#trade-offs#decision-making#pattern-selection
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill architecture-pattern-selection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-pattern-selection
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/architecture-pattern-selection/skills/architecture-pattern-selection
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill architecture-pattern-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers need a disciplined method to select the most suitable architectural pattern for a system based on concrete context factors, rather than defaulting to a single pattern.

Core Features & Use Cases

  • Monolith-first analysis: start with a simple solution and justify moving to distributed patterns only when needed.
  • Phase-based decision framework: handles input, catalogs patterns, scores decision factors, and guides evolution.
  • Hybrid recommendations: supports combining patterns (e.g., modular monolith core with microservice edges) and async integration.
  • Evolution roadmaps and diagrams: provides pattern comparison and evolution timelines to plan transitions.

Quick Start

Provide system context and constraints to receive a recommended architectural pattern with trade-offs and an evolution roadmap.

Frequently Asked Questions about architecture-pattern-selection

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

FAQPage Schema
How do I choose between a monolith and microservices architecture for a new system?▼

You can select an architectural pattern by providing system context and constraints to receive a recommendation with explicit trade-offs and a documented evolution roadmap.

What architectural patterns are available for context-driven selection?▼

Context-driven pattern selection applies to monolith, modular monolith, microservices, event-driven, serverless, CQRS, service-based, and space-based patterns, evaluating each against your specific system context factors.

Can I combine multiple architectural patterns like a modular monolith with microservices?▼

Yes, hybrid recommendations support combining patterns like a modular monolith core with microservice edges and async integration, scoring decision factors to guide the evolution roadmap.

How do I plan an evolution roadmap for migrating from a monolith to microservices?▼

Pattern selection provides phase-based decision frameworks that generate evolution roadmaps and diagrams, mapping out timelines and reversibility considerations for transitioning from monolith to distributed architectures.

When should I not use microservices and stick with a monolith architecture?▼

A monolith-first approach enforces starting simple, meaning you should avoid distributed patterns unless explicit context factors and trade-off justifications demonstrate the need for microservices.

Related Skills

Explore More Software Engineering Skills→
2good4me2good4me

architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions in ADR format.

Community
Advanced
vuminhieuvuminhieu

planning

Create structured technical plans with architectural designs and implementation roadmaps.

Community
Advanced
wesleyosantos91wesleyosantos91
6

aws-architecture-patterns

Design AWS serverless architectures with API Gateway, Lambda, SQS, EventBridge, Step Functions, and DynamoDB.

Community
Advanced
xcrrrxcrrr
4

architecture-designer

Guide architecture pattern selection and document decisions with ADRs.

Community
Advanced