Skill

role-architect:system-design

System design expertise including requirements analysis, C4 model diagrams, sequence diagrams, data flow diagrams, trade-off documentation, capacity estimation, distributed systems theory, load balancing algorithms, caching architectures, message-driven and stream processing architectures, data pipeline design, search architecture, and system design patterns for common internet-scale systems (URL shorteners, chat, news feed, rate limiters).

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-architect

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Designing a new system or major feature from scratch

Supporting Assets

references/distributed-systems-theory.mdreferences/load-balancing-and-caching.mdreferences/messaging-streaming-and-patterns.mdreferences/requirements-and-diagrams.md

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

market-sizing-analysis

2 files

Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.

startup-business-analyst

32.9k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-architect:system-design

When to use

Designing a new system or major feature from scratch

Evaluating trade-offs between architectural approaches

Estimating capacity for a given load profile

Choosing between consistency and availability models

Architecting message-driven, event-driven, or stream processing systems

Preparing for or conducting a system design review

Core principles

Requirements first — no architecture without explicit functional and non-functional targets

Diagrams as communication — C4 model from context down to component; sequence diagrams for every critical flow

Trade-offs are mandatory — every decision needs at least two alternatives documented

Capacity estimation gates the design — estimate before you commit to a technology

Distributed systems lie — CAP/PACELC, consensus, and eventual consistency have real operational consequences

Reference Files

references/requirements-and-diagrams.md — functional/non-functional requirements, C4 model (all four levels), sequence diagrams, data flow diagrams, trade-off documentation, and capacity estimation formulas

references/distributed-systems-theory.md — CAP theorem, PACELC theorem, Raft/Paxos/Zab consensus algorithms, vector clocks, Lamport timestamps, CRDTs, and eventual consistency patterns (read repair, anti-entropy, hinted handoff)

references/load-balancing-and-caching.md — round-robin/least-connections/consistent hashing/Maglev/power-of-two-choices algorithms; cache-aside/write-through/write-behind/read-through/multi-layer caching; Redis Cluster patterns and hot key mitigation

references/messaging-streaming-and-patterns.md — message queue patterns, event-driven architecture (event sourcing, outbox, saga), Kafka Streams, Apache Flink, Spark Structured Streaming, Lambda/Kappa architectures, search engines (Elasticsearch/Meilisearch/Algolia), and common system design problems (URL shortener, rate limiter, chat, news feed, notifications)

System Design

When to use

Designing a new system or major feature from scratch
Evaluating trade-offs between architectural approaches
Estimating capacity for a given load profile
Choosing between consistency and availability models
Architecting message-driven, event-driven, or stream processing systems
Preparing for or conducting a system design review

Core principles

Requirements first — no architecture without explicit functional and non-functional targets
Diagrams as communication — C4 model from context down to component; sequence diagrams for every critical flow
Trade-offs are mandatory — every decision needs at least two alternatives documented
Capacity estimation gates the design — estimate before you commit to a technology
Distributed systems lie — CAP/PACELC, consensus, and eventual consistency have real operational consequences

Reference Files

references/requirements-and-diagrams.md — functional/non-functional requirements, C4 model (all four levels), sequence diagrams, data flow diagrams, trade-off documentation, and capacity estimation formulas
references/distributed-systems-theory.md — CAP theorem, PACELC theorem, Raft/Paxos/Zab consensus algorithms, vector clocks, Lamport timestamps, CRDTs, and eventual consistency patterns (read repair, anti-entropy, hinted handoff)
references/load-balancing-and-caching.md — round-robin/least-connections/consistent hashing/Maglev/power-of-two-choices algorithms; cache-aside/write-through/write-behind/read-through/multi-layer caching; Redis Cluster patterns and hot key mitigation
references/messaging-streaming-and-patterns.md — message queue patterns, event-driven architecture (event sourcing, outbox, saga), Kafka Streams, Apache Flink, Spark Structured Streaming, Lambda/Kappa architectures, search engines (Elasticsearch/Meilisearch/Algolia), and common system design problems (URL shortener, rate limiter, chat, news feed, notifications)