system-design

仓库创建 2026年7月27日最近提交 1 天前SkillHot 收录 1 天前
▸ 精选理由

适合架构评审与容量/可用性权衡的技术顾问。

这个 Skill 做什么

帮助设计与评审系统架构,涵盖扩展性、CAP、缓存等决策。

帮你把分布式系统的大方向定下来:从扩展性、CAP 权衡、缓存、分片到负载均衡和容量估算都会考虑。适合在写 architecture proposal、做设计评审、选 REST/gRPC/GraphQL 或队列,或准备把系统横向扩容时使用。特别之处是给出可量化的可用性/容量计算和工程化决策依据,把抽象讨论变成可执行方案。

▸ 展开 SKILL.md 英文原文

Designs and reviews system architecture: scalability, CAP trade-offs, caching, sharding, queues, load balancing, availability math, capacity estimates. Use for architecture decisions, design docs, choosing between REST/gRPC/GraphQL/queues, or "how should we structure/scale this".

开发编程系统设计架构评审容量规划通用
0
Stars
0
Forks
21
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/system-design/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/system-design/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# System Design

Knowledge skill. Rules are numbered with RFC-2119 keywords — cite them in reviews ("violates rule #9").

## When to use

Use for: architecture proposals and reviews, design docs, scaling an existing system, choosing datastores/protocols/queues, capacity planning, availability targets, cache/shard strategy.

Do NOT use for: code-level refactors inside one service, UI design, algorithm puzzles, or writing Terraform/K8s manifests for an already-decided design.

## Method — 4 steps, always in this order

1. **Use cases, constraints, capacity.** Write the top 3 use cases, explicit non-goals, and the numbers: DAU, QPS (avg + peak), read:write ratio, latency SLO, availability targe
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有