system-design

Designs systems, services, and architectures with requirements, components, and trade-offs.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill system-design-8gg-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/8GG-Git/knowledge-work-plugins/tree/main/engineering/skills/system-design
Command: npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill system-design-8gg-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists in designing complex systems, services, and architectures, ensuring all critical aspects from requirements to scalability are considered.

Core Features & Use Cases

  • Requirements Gathering: Defines functional and non-functional requirements.
  • High-Level Design: Creates component diagrams, data flows, and API contracts.
  • Deep Dive: Details data models, API endpoints, caching, and error handling.
  • Scale and Reliability: Addresses load estimation, failover, and monitoring.
  • Trade-off Analysis: Explicitly documents design decisions and their implications.
  • Use Case: When building a new e-commerce platform, use this Skill to outline the architecture, including microservices, database choices, and scaling strategies.

Quick Start

Design a scalable e-commerce platform for a growing online retailer.

Frequently Asked Questions about system-design

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

FAQPage Schema
How do I design a scalable system architecture for a new platform?

To design a scalable system architecture, gather functional and non-functional requirements, define high-level components and data flows, and analyze trade-offs for scale and reliability. This ensures all critical aspects from requirements to scalability are considered.

What is the best way to define service boundaries and API contracts?

The best way to define service boundaries and API contracts is through high-level design mapping component diagrams and data flows, followed by a deep dive into API endpoints, data modeling, and error handling.

How do you estimate load and plan for failover in distributed systems?

Estimating load and planning failover in distributed systems involves addressing scale and reliability explicitly by calculating capacity estimates, defining failover mechanisms, and establishing monitoring strategies.

Can I analyze trade-offs when choosing database models and caching strategies?

Yes, you can analyze trade-offs for database models and caching strategies by explicitly documenting design decisions and their implications, ensuring architecture choices align with scale and reliability requirements.

What steps are needed to document functional and non-functional requirements for microservices?

Documenting functional and non-functional requirements for microservices requires gathering initial constraints, creating high-level component diagrams, and detailing data models and API endpoints to outline the architecture.