system-design

Guide system design pattern selection for distributed systems architectures.

14|3|Updated Feb 22, 2026

Search Tags:#architecture #scalability #system design #microservices #distributed systems #monolith #event-driven

Ready to run

npx skills add https://github.com/rnavarych/alpha-engineer --skill system-design-rnavarych

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/billy-milligan/skills/architecture/system-design
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill system-design-rnavarych

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps engineers make informed decisions about system architecture, guiding them from monolithic structures to scalable distributed systems.

Core Features & Use Cases

Architecture Selection: Choose between monolith, modular monolith, and microservices based on team size, traffic, and complexity.
Pattern Implementation: Understand and apply patterns like event-driven architecture, strangler fig, CQRS, and cell-based designs.
Scaling Strategies: Provides guidance on traffic thresholds, database scaling, and caching.
Use Case: A startup is deciding whether to continue with their monolith or break it into microservices as they grow. This Skill provides a framework and data points to make that critical decision.

Quick Start

Use the system-design skill to evaluate if we should migrate from a monolith to microservices given our current team size and traffic.

Frequently Asked Questions about system-design

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

FAQPage Schema

When should I migrate from a monolith to microservices?▼

Decompose your monolith into microservices when team size and traffic thresholds demand independent scaling. This Skill provides data points and frameworks to evaluate if modular monoliths or distributed systems fit your growth stage.

What is the strangler fig pattern for decomposing distributed systems?▼

The strangler fig pattern incrementally replaces monolith components with microservices. This Skill provides principles for applying it alongside event-driven architecture and CQRS to safely decompose distributed systems.

How do I choose between a modular monolith and microservices for my architecture?▼

Select between monolith, modular monolith, and microservices by analyzing team size, traffic volume, and complexity. This Skill provides frameworks to match your architecture pattern to current operational demands.

How does event-driven architecture work for scaling distributed systems?▼

Event-driven architecture scales distributed systems by asynchronously routing events between decoupled services. This Skill provides guidance on implementing it alongside CQRS and cell-based architecture for reliable scaling.

What are the limitations of moving to a distributed systems architecture?▼

Distributed systems introduce operational complexity in traffic management and data consistency. This Skill helps navigate limitations by providing scaling principles, caching strategies, and cell-based architecture patterns to mitigate risk.