用于按七步法系统审查架构设计,识别风险、权衡并产出改进建议。
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "systems-design-review-methodology" 技能: 1. 下载 https://raw.githubusercontent.com/microsoft/amplifier-bundle-systems-design/main/skills/systems-design-review-methodology/SKILL.md 2. 保存为 ~/.claude/skills/systems-design-review-methodology/SKILL.md 3. 装好后重载技能,告诉我可以用了
请按 systems-design-review-methodology 的七步法,评审这个电商平台的微服务架构方案:先总结设计目标与约束,再分类系统类型,检查是否符合现有代码库与团队能力,做对抗性风险分析,验证扩展性/一致性/成本权衡,最后给出结论和行动项。
一份结构化设计评审结果,包含主要风险、关键权衡、与现状不匹配点及可执行改进建议。
请用七步设计评审法分析这个日志处理系统:系统每天处理 50TB 日志,要求低延迟检索和低成本存储。请重点审查瓶颈、故障场景、安全边界,以及方案中的技术取舍是否合理。
一份覆盖性能、可靠性、安全与成本的评审报告,并附带优先级明确的优化行动项。
我准备把单体应用拆分为事件驱动架构。请按照 systems-design-review-methodology 评审这个迁移设计,重点判断它与现有代码库、部署流程、监控体系和团队维护能力是否匹配,并指出需要用户进一步确认的关键决策点。
一份面向迁移决策的审查结论,说明适配性、潜在实施风险和需要确认的前置条件。
Companion skill for the /systems-design-review mode. The mode gates tools; this skill governs behavior.
For automated staging with approval gates, use the systems-design-review recipe instead of this manual flow:
recipes(operation="execute", recipe_path="@systems-design:recipes/systems-design-review.yaml", context={"target_path": "<path>"})
The recipe automates reconnaissance, classification, multi-perspective analysis, and report generation with human checkpoints between stages.
You handle the CONVERSATION. Agents handle the ANALYSIS.
You guide the user through the review, synthesize findings, and facilitate decisions. For deep analysis work, delegate to systems-design:systems-design-critic or use the adversarial-review skill.
Before any critique, reconstruct the designer's reasoning:
Apply the Comprehending Existing lens:
Understanding original intent prevents reviews that recommend "fixing" things the designer already considered and deliberately chose.
Ask: "Is this the complete design, or is there additional context I should know about?"
This step is mandatory. Do not skip it. Do not proceed to analysis without completing it.
Based on what you learned in Step 1, classify the system under review. Produce a brief taxonomy:
System types -- which of these apply? List ALL that match, not just the primary one:
| Type | Skill | Applies when... |
|---|---|---|
| Web service / API | system-type-web-service | HTTP endpoints, REST/GraphQL, request-response |
| Event-driven | system-type-event-driven | Message queues, event logs, pub/sub, hooks, reactive patterns |
| Data pipeline | system-type-data-pipeline | Batch/streaming processing, ETL, DAG scheduling |
| Workflow orchestration | system-type-workflow-orchestration | Multi-step processes, sagas, durable execution |
| CLI tool | system-type-cli-tool | Command-line interface, subcommands, plugin architecture |
| Real-time | system-type-real-time | WebSockets, persistent connections, state sync |
| Multi-tenant SaaS | system-type-multi-tenant-saas | Tenant isolation, shared infrastructure, billing |
| ML serving | system-type-ml-serving | Model serving, feature stores, inference pipelines |
| Distributed system | system-type-distributed | Consensus, replication, partitioning, multi-node coordination |
| Enterprise integration | system-type-enterprise-integration | Legacy modernization, API gateways, data integration |
| Edge / offline-first | system-type-edge-offline | Offline operation, sync protocols, constrained resources |
| Single-page app | system-type-spa | Client-side routing, state management, rendering strategies |
| Peer-to-peer | system-type-peer-to-peer | P2P topologies, NAT traversal, decentralized coordination |
| Azure-hosted | system-type-azure | Azure compute, identity, networking, managed services |
Design philosophies -- which does the system claim or embody?
| Philosophy | Skill | Applies when... |
|---|---|---|
| Linux/Unix | design-philosophy-linux | Mechanism vs policy, composability, small sharp tools |
| Domain-driven | design-philosophy-domain-driven | Bounded contexts, ubiquitous language, aggregates |
…
帮助设计可离线运行的边缘系统,处理同步、冲突恢复与弱网故障场景。
帮助设计与评估企业系统集成方案,覆盖遗留改造、网关、事件与失效模式。
用 Unix/Linux 设计哲学评估系统方案的可组合性、简洁性与关注点分离。
帮助用户设计或评估基于 Azure 的系统架构与运维方案
帮助设计与评估数据管道架构,覆盖批流处理、调度、质量与故障策略。
帮助设计和评估多租户SaaS的平台隔离、计量计费与稳定性方案
用于按九阶段方法系统化推进架构设计、权衡取舍与迁移规划。
从六个关键角色视角审查系统设计,并输出统一风险评估建议
用于架构设计与代码实现阶段的安全审查,识别威胁、漏洞与合规风险。
用于代码与分支审查,综合检查正确性、兼容性、架构、测试、性能与安全问题。
帮助生成或审查设计系统,检查视觉一致性并评审样式相关改动。
审查实现计划中的遗漏、假设与步骤顺序,降低后续开发返工风险