Verified:GitHub

system-design

Design system architectures with requirements analysis, API contracts, and trade-off evaluation.

3|Updated Jun 29, 2026

Search Tags:#architecture #scalability #system design #api design #data modeling #distributed systems #trade-off analysis

Ready to run

npx skills add https://github.com/ruskicoder/system-prompts --skill system-design-ruskicoder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/system-design
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill system-design-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a structured framework for designing systems and evaluating architectural decisions, preventing ad-hoc designs that ignore scale, reliability, and trade-offs. ## Core Features & Use Cases - Requirements Gathering: Captures functional and non-functional requirements including scale, latency, availability, and cost constraints. - High-Level and Deep Design: Produces component diagrams, data flows, API contracts (REST, GraphQL, gRPC), data models, caching strategies, and queue designs. - Scale and Trade-off Analysis: Covers load estimation, horizontal vs. vertical scaling, failover, monitoring, and explicit trade-off documentation. - Use Case: When asked to design a notification service, it walks through requirements, proposes an architecture with queues and retry logic, and documents what to revisit as the system grows. ## Quick Start Ask the AI to design a system for your use case, for example: design a system for a real-time chat application supporting one million concurrent users.

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 system architecture from scratch?▼

Start by gathering functional and non-functional requirements, then produce a high-level design with component diagrams, data flow, and API contracts. Follow with deep dives into data models, caching, and queues, then analyze scale, reliability, and trade-offs.

How to choose between REST, GraphQL, and gRPC for API design?▼

The choice depends on your use case: REST suits simple resource-based APIs, GraphQL fits flexible client-driven queries, and gRPC works best for high-performance internal service communication. The skill covers API endpoint design across all three during the deep-dive phase.

What should a system design document include?▼

A design document should include requirements, a component diagram, data flow, API contracts, storage choices, caching and queue strategies, error handling, load estimates, and explicit trade-off analysis. It should also note what to revisit as the system grows.

When should I use horizontal vs vertical scaling?▼

Vertical scaling (bigger machines) is simpler but has hardware limits and single points of failure. Horizontal scaling (more machines) supports higher availability and growth but adds complexity in data distribution and failover, which the skill's scale and reliability phase addresses.

Does this skill produce actual architecture diagrams?▼

It produces ASCII or described diagrams within structured design documents, along with explicit assumptions and trade-off analysis. It does not generate image files or integrate with diagramming tools.