system-design

Evaluate architectural trade-offs and capacity requirements for scalable software services.

25|3|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill system-design-nimadorostkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/development/system-design
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill system-design-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift and oversight by forcing a structured, honest evaluation of system constraints, failure modes, and scaling limits before a single line of code is written.

Core Features & Use Cases

  • Capacity Estimation: Perform arithmetic-backed calculations for throughput, storage, and latency requirements.
  • Failure Analysis: Systematically identify how dependencies impact availability and performance under stress.
  • Trade-off Documentation: Explicitly define non-goals and rejected alternatives to ensure the design remains focused and maintainable.

Quick Start

Use the system-design skill to evaluate the proposed architecture for our new user notification service and identify potential scaling bottlenecks.

Frequently Asked Questions about system-design

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

FAQPage Schema
What is the best way to perform capacity planning for existing infrastructure?

Capacity planning for existing infrastructure requires arithmetic-backed calculations for throughput, storage, and latency requirements to accurately estimate system constraints and identify scaling limits under stress.

Can I use this structured framework to prepare an RFC for a new user notification service?

Modeling failure modes involves systematically identifying how dependencies impact availability and performance under stress, ensuring an honest evaluation of system constraints and failure scenarios during the architecture process.

How do I model failure modes and analyze dependency impact on system availability?

Failure analysis systematically identifies how dependencies impact availability and performance under stress, while trade-off documentation explicitly defines non-goals and rejected alternatives to keep the system design focused and maintainable.

What is the best way to perform capacity planning for existing infrastructure?

Documenting non-goals and rejected alternatives during system design prevents architectural drift and oversight by forcing a structured, honest evaluation of constraints, ensuring the architecture remains focused and maintainable over time.