mcpField
S
System Design

System Design

github.com/danhvbDevelopment94 installs
Repository

About System Design

A system design skill for the Solution Architect Agent, covering architectural patterns, quality attributes, API and database choices, and architecture documentation. It supports deliverables such as high- and low-level designs.

Key features

  1. 01Compare monoliths, microservices, and other patterns
  2. 02Review scalability and reliability decisions
  3. 03Outline REST, GraphQL, and gRPC options
  4. 04Distinguish relational and NoSQL databases
  5. 05Cover C4 and ADR documentation
  6. 06List HLD, LLD, and other deliverables

Use cases

  1. 01Choose a pattern for a new system
  2. 02Assess availability and security decisions
  3. 03Plan API and database approaches
  4. 04Prepare design documents and decision records

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/danhvb/my-ba-skills --skill system-design

After installing, type/system-designin Claude Code to confirm it loaded.

Details

From the project README

System Design Skill

Purpose

Enable the Solution Architect Agent to design the high-level structure of software systems, selecting appropriate patterns, technologies, and integration strategies.

Architectural Patterns

1. Monolithic
  • Use Case: Small startup, simple domain, fast initial dev.
  • Pros: Simple deployment, easy debugging.
  • Cons: Scalability limits, tight coupling.
2. Microservices
  • Use Case: Complex enterprise, distinct domains, independent scaling.
  • Pros: Tech stack agnostic per service, scalable.
  • Cons: Distributed complexity, network latency, data consistency.
3. Event-Driven
  • Use Case: Real-time interactions, high decoupling.
  • Components: Producers, Consumers, Event Bus (Kafka, RabbitMQ).
4. Serverless
  • Use Case: Event-triggered, variable load.
  • Pros: Pay-per-use, no infra management.

Key Design Decisions (The "ilities")

  • Scalability: Vertical (bigger machine) vs. Horizontal (more machines).
  • Availability: Redundancy, failover strategies. Load balancers.
  • Reliability: Circuit breakers, retries, eventual consistency.
  • Maintainability: Clean code, documentation, monitoring.
  • Security: Authentication (OAuth), Authorization (RBAC), Encryption.

API Design Strategy

  • REST: Standard resource-based.
  • GraphQL: Flexible data querying.
  • gRPC: High performance inter-service comms.

Database Selection

  • Relational (SQL): Structured data, ACID transactions (PostgreSQL, MySQL).
  • NoSQL (Document): Flexible schema, rapid iteration (MongoDB).
  • NoSQL (Key-Value): Caching, heavy read/write (Redis, DynamoDB).
  • Time-Series: IoT, financial data (InfluxDB).

Documenting Architecture

  • C4 Model: Context, Container, Component, Code.
  • ADR (Architecture Decision Records): Documenting WHY a decision was made.

Deliverables

  • High-Level Design (HLD) Document.
  • Low-Level Design (LLD) Document.
  • Database Schema (ERD).
  • API Specifications (Swagger/OpenAPI).

Comments

Markdown supported