Index of every page on this site: llms.txt
All skills
anthropics avatar

/system-design

@b4c9a4e
Run it yourself

Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

Use this Skill: https://skilld.dev/gh/anthropics/knowledge-work-plugins/system-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈66 tokens for metadata: the name and description. ≈255 when used: this file.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈264 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

System Design

Help design systems and evaluate architectural decisions.

Framework

1. Requirements Gathering

  • Functional requirements (what it does)
  • Non-functional requirements (scale, latency, availability, cost)
  • Constraints (team size, timeline, existing tech stack)

2. High-Level Design

  • Component diagram
  • Data flow
  • API contracts
  • Storage choices

3. Deep Dive

  • Data model design
  • API endpoint design (REST, GraphQL, gRPC)
  • Caching strategy
  • Queue/event design
  • Error handling and retry logic

4. Scale and Reliability

  • Load estimation
  • Horizontal vs. vertical scaling
  • Failover and redundancy
  • Monitoring and alerting

5. Trade-off Analysis

  • Every decision has trade-offs. Make them explicit.
  • Consider: complexity, cost, team familiarity, time to market, maintainability

Output

Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured framework for architectural system design and contains no executable code or security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b4c9a4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago
  • system-design
  • architecture
  • api-design
  • data-modeling
  • scalability
  • reliability
  • trade-offs
  • service-design

README badge

README badge for anthropics/knowledge-work-plugins/system-design

Guides architectural decisions through structured requirements gathering, component design, data modeling, and trade-off analysis. Useful when designing APIs, service boundaries, or evaluating scaling strategies for distributed systems.

Generated from the current SKILL.md.

When should I trigger this skill?
Use it when you need help designing a system architecture, evaluating API design, modeling data structures, or defining service boundaries. Common triggers include 'design a system for', 'how should we architect', or 'what's the right architecture for'.
Does this skill produce diagrams?
Yes. It generates component diagrams and data flow visualizations in ASCII or described format, not just text.
What does the skill cover in its design process?
It covers requirements gathering, high-level design, deep dives into data models and APIs, scale and reliability analysis, and explicit trade-off analysis for every architectural decision.
Does this help with specific technologies or is it framework-agnostic?
It's framework-agnostic and works with any tech stack. It considers your existing constraints and team familiarity as part of the trade-off analysis.

Generated from the current SKILL.md. These answers refresh after source changes.