skills.rest
alirezarezvani
alirezarezvaniCOMMUNITY
Explore all skills by this author →
Website𝕏@RezaRezvaniBlnGitHub

architecture-pattern-selector

Select optimal architecture patterns using scoring factors like team size and DevOps maturity.

110|19|Updated Dec 4, 2025
Search Tags:#architecture#migration#decision#pattern#monolith#scoring
One-click install
npx skills add https://github.com/alirezarezvani/claude-cto-team --skill architecture-pattern-selector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-pattern-selector
Source: https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/architecture-pattern-selector
Command: npx skills add https://github.com/alirezarezvani/claude-cto-team --skill architecture-pattern-selector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams select the most effective architecture pattern for a project, avoiding over- or under-engineering.

Core Features & Use Cases

  • Framework-driven pattern selection across Monolith, Modular Monolith, Microservices, Serverless.
  • Built-in scoring and decision matrix to guide migration paths and trade-offs for teams of varying sizes and DevOps maturity.
  • Practical guidance on migration paths and identifying when to stop and refactor.

Quick Start

Provide your project constraints and let the selector return a recommended architecture pattern.

Frequently Asked Questions about architecture-pattern-selector

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

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

Choosing the right architecture pattern requires a structured selection framework that evaluates constraints like team size, expected scale, and DevOps maturity to recommend monolith, modular monolith, microservices, or serverless.

When should I migrate from a monolith to microservices?▼

Migrating from a monolith to microservices is justified when a structured scoring framework determines your DevOps maturity and expected scale justify the migration path and its associated trade-offs.

What is the best way to decide between a modular monolith and serverless architecture?▼

Deciding between a modular monolith and serverless is best achieved by applying a decision matrix that scores factors like team size and DevOps maturity to map out specific trade-offs and migration paths.

How do I evaluate architecture trade-offs for a platform re-architecture?▼

To evaluate architecture trade-offs for a platform re-architecture, score expected scale and DevOps maturity to identify when to stop and refactor across monolith, modular monolith, microservices, or serverless patterns.

Does team size affect architecture pattern selection for new systems?▼

Team size directly affects architecture pattern selection for new systems by acting as a primary scoring factor alongside expected scale and DevOps maturity to prevent over- or under-engineering.

Related Skills

Explore More Software Engineering Skills→
jetmobsoljetmobsol

architecture-pattern-selector

Recommend software architecture patterns based on project constraints and trade-offs.

Community
Intermediate
agnaldo4jagnaldo4j
1

microservices-modular-monolith

Evaluate architectural boundaries to determine modular monolith to microservices transition paths.

Community
Advanced
softsparksoftspark
161

architecture-decision

Document architecture decisions with structured templates for context, consequences, and trade-offs.

Community
Advanced
sncollectivesncollective

scan-performance

Detect performance issues in SNC codebase queries, layout, loading, and bundles.

Official
Intermediate