system-design-verifier
Audit architectures against failure modes (resilience, scalability, consistency, security). Use when reviewing a new system design or architecture proposal, before major infrastructure changes, or during post-incident analysis of architectural weaknesses.
- License 许可
- MIT
- 所属仓库
- muratovv/ai-hats
- 最近更新
- 2026-11-05
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- system-design-verifier
- license
- MIT
- description
- Audit architectures against failure modes (resilience, scalability, consistency, security). Use when reviewing a new system design or architecture proposal, before major infrastructure changes, or during post-incident analysis of architectural weaknesses.
03 SKILL.md 正文
System Design Verifier
Audit proposed or existing architectures against common failure modes.
When to Use
Whole-system / proposal-level audit against failure modes (resilience, scalability, consistency, security). Narrower siblings: intra-service layering and dependency direction → clean-architecture-guide; the specific failure modes of crossing a network boundary → distributed-systems-checklist. Use this for the system silhouette, those for the pieces inside it.
Procedure
- Identify Interfaces: Map all network boundaries (REST, gRPC, queues, DB connections).
- Verify Resilience: For each boundary — what happens if this dependency is down or slow? Ensure timeouts, retries, and circuit breakers are designed.
- Verify Scalability: Identify stateful components. Can they scale horizontally? Are there single points of failure?
- Verify Consistency: Is data eventually consistent or strongly consistent? Does the business logic handle eventual consistency correctly (e.g., Sagas for distributed transactions)?
- Verify Security: Are interfaces authenticated? Are trust boundaries documented? Is data encrypted in transit and at rest?
- Report: Produce a structured findings list: component, risk, severity, recommendation.
Completion
- All interfaces mapped and verified across 4 dimensions (resilience, scalability, consistency, security)
- Findings report produced with severity and recommendations
Anti-Patterns
- Reviewing only the happy path — failure modes are the whole point
- Ignoring data consistency model — leads to subtle bugs under load
- No severity ranking — treating all findings equally dilutes focus
04 同仓库更多 Skills
tool-evaluation-protocol
Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML/LLM frameworks, testing approaches), or following up on a hype-driven recommendation.
systematic-debugging
4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.
skill-template
Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.
skill-optimization
Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.
silent-fallback-gate
PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.
retro-to-framework
Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.