系统 设计
- 作者仓库星标 19,014
- 作者仓库 knowledge-work-plugins
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.
- 流狐分类
- 设计与多媒体
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @anthropics · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 允许外网请求
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Framework
Functional requirements (what it does) Non-functional requirements (scale, latency, availability, cost) Constraints (team size, timeline, existing tech stack)
Component diagram Data flow API contracts
Data model design API endpoint design (REST, GraphQL, gRPC) Caching strategy
Load estimation Horizontal vs. vertical scaling Failover and redundancy
Every decision has trade-offs. Make them explicit. Consider: complexity, cost, team familiarity, time to market, maintainability
# 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.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Framework → 1. Requirements Gathering → 2. High-Level Design → 3. Deep Dive → 4. Scale and Reliability → 5. Trade-off Analysis
要点 -> Help design systems and evaluate architectural decisions. · Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis.
文件/命令 -> Queue/event
内容 SHA-256 -> 9a0479e16073
方法与流程
适用与边界
原文中的明确线索
Queue/event