system design
- Repo stars 19,014
- Author repo knowledge-work-plugins
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @anthropics · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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.
Sections and files
Listed in source order.
sections -> Framework → 1. Requirements Gathering → 2. High-Level Design → 3. Deep Dive → 4. Scale and Reliability → 5. Trade-off Analysis
terms -> Help design systems and evaluate architectural decisions. · Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis.
files/cmd -> Queue/event
body sha256 -> 9a0479e16073
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