system-design

Design system architectures for web services, APIs, and distributed systems.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill system-design-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/engineering-system-design
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill system-design-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams design robust, scalable, and maintainable systems and architectures, bridging requirements to concrete design decisions.

Core Features & Use Cases

  • Requirements gathering and constraints mapping.
  • High-level design with component diagrams, data flows, and API contracts.
  • Deep dive into data models, API endpoints, caching, queues, and error handling.
  • Trade-off analysis and scalability planning.

Quick Start

Provide a complete system design outline for a new service based on given requirements.

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 web service?

To design a scalable system architecture, start by gathering functional and non-functional requirements, then map out high-level components, data flows, and API contracts to meet those service constraints.

What is the best way to analyze trade-offs in distributed systems design?

Analyzing trade-offs in distributed systems design involves evaluating scalability and reliability decisions against constraints, comparing data modeling and API design choices to determine the most robust architecture.

How does system design help bridge requirements and concrete data models?

System design bridges requirements to concrete data models by guiding decisions from high-level components down to specific interfaces, ensuring data flows and API endpoints satisfy functional needs.

Can I use this approach for both API design and data platform architecture?

Yes, this system design approach applies to web services, APIs, data platforms, and distributed systems, guiding comprehensive decisions from component diagrams to interface definitions.

When do I need to map constraints during the high-level design process?

You need to map constraints during the high-level design process when defining non-functional requirements, ensuring that component diagrams, caching, and queues satisfy scalability and reliability targets.