[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGX7SRDGH5SQVM7HTVQ3C0":3,"skill-same:01M6JGX7SRDGH5SQVM7HTVQ3C0":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6JGX7SRDGH5SQVM7HTVQ3C0","system-design-verifier",null,"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.","muratovv\u002Fai-hats","muratovv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7502801?v=4","01M6JGCBN4KEJX012GPJVSH04T","Fedor Muratov","01M6JGCBSNMN7CW3RGTPPE0MN2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fsystem-design-verifier\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"system design verifier","system","system design","design","verifier","incident","modes","changes","consistency","architectures","post","proposal","scalability","use","analysis","post-incident","audit","resilience","architecture","security","2026-11-10 10:12:30",false,"---\nname: system-design-verifier\ndescription: >-\n  Audit architectures against failure modes (resilience, scalability,\n  consistency, security). Use when reviewing a new system design or\n  architecture proposal, before major infrastructure changes, or during\n  post-incident analysis of architectural weaknesses.\nlicense: MIT\n---\n# System Design Verifier\n\nAudit proposed or existing architectures against common failure modes.\n\n## When to Use\nWhole-system \u002F proposal-level audit against failure modes (resilience,\nscalability, consistency, security). Narrower siblings: intra-service layering\nand dependency direction → **clean-architecture-guide**; the specific failure\nmodes of crossing a network boundary → **distributed-systems-checklist**. Use\nthis for the system silhouette, those for the pieces inside it.\n\n## Procedure\n1. **Identify Interfaces:** Map all network boundaries (REST, gRPC, queues, DB connections).\n2. **Verify Resilience:** For each boundary — what happens if this dependency is down or slow? Ensure timeouts, retries, and circuit breakers are designed.\n3. **Verify Scalability:** Identify stateful components. Can they scale horizontally? Are there single points of failure?\n4. **Verify Consistency:** Is data eventually consistent or strongly consistent? Does the business logic handle eventual consistency correctly (e.g., Sagas for distributed transactions)?\n5. **Verify Security:** Are interfaces authenticated? Are trust boundaries documented? Is data encrypted in transit and at rest?\n6. **Report:** Produce a structured findings list: component, risk, severity, recommendation.\n\n## Completion\n- All interfaces mapped and verified across 4 dimensions (resilience, scalability, consistency, security)\n- Findings report produced with severity and recommendations\n\n## Anti-Patterns\n- Reviewing only the happy path — failure modes are the whole point\n- Ignoring data consistency model — leads to subtle bugs under load\n- No severity ranking — treating all findings equally dilutes focus\n","# System Design Verifier\n\nAudit proposed or existing architectures against common failure modes.\n\n## When to Use\nWhole-system \u002F proposal-level audit against failure modes (resilience,\nscalability, consistency, security). Narrower siblings: intra-service layering\nand dependency direction → **clean-architecture-guide**; the specific failure\nmodes of crossing a network boundary → **distributed-systems-checklist**. Use\nthis for the system silhouette, those for the pieces inside it.\n\n## Procedure\n1. **Identify Interfaces:** Map all network boundaries (REST, gRPC, queues, DB connections).\n2. **Verify Resilience:** For each boundary — what happens if this dependency is down or slow? Ensure timeouts, retries, and circuit breakers are designed.\n3. **Verify Scalability:** Identify stateful components. Can they scale horizontally? Are there single points of failure?\n4. **Verify Consistency:** Is data eventually consistent or strongly consistent? Does the business logic handle eventual consistency correctly (e.g., Sagas for distributed transactions)?\n5. **Verify Security:** Are interfaces authenticated? Are trust boundaries documented? Is data encrypted in transit and at rest?\n6. **Report:** Produce a structured findings list: component, risk, severity, recommendation.\n\n## Completion\n- All interfaces mapped and verified across 4 dimensions (resilience, scalability, consistency, security)\n- Findings report produced with severity and recommendations\n\n## Anti-Patterns\n- Reviewing only the happy path — failure modes are the whole point\n- Ignoring data consistency model — leads to subtle bugs under load\n- No severity ranking — treating all findings equally dilutes focus\n",{"name":5,"license":15,"description":7},"master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fsystem-design-verifier",1,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add muratovv\u002Fai-hats --skill system-design-verifier",{"tool":67,"command":68},"bunx","bunx skills add muratovv\u002Fai-hats --skill system-design-verifier",{"tool":70,"command":71},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill system-design-verifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fsystem-design-verifier\u002FSKILL.md",true,[],[76,102,127,148,171,185],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":49},"01M6PVFB1SM738R2SRSRSF7CY6","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\u002FLLM frameworks, testing approaches), or following up on a hype-driven recommendation.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Ftool-evaluation-protocol\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,42,93,94,95,96,97,98,99,100,101],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","dependency","up","frameworks","time","project","recommendation","for","bounded","candidate",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":49},"01M6PVF7HATBEX1G7N50E2QT57","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.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[109,110,111,112,83,113,114,115,116,117,42,118,119,120,121,122,123,124,125,126],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","with","bug-fix","phase",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":49},"01M6PVF3MTQN3RPF73AN34856J","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.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-template\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[137,138,139,140,141,116,142,42,143,121,144,145,146,99,147],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":49},"01M6PVF06SCV28QARM5MQPANC9","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.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-optimization\u002FSKILL.md",[154],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,158,159,160,161,45,162,163,164,42,165,166,167,168,169,170],"Optimization","skill optimization","components","component","issues","library","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":49},"01M6PVEXM9717016T9MW82HDCT","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.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsilent-fallback-gate\u002FSKILL.md",[],[178,179,180,181,182,183,42,184,99],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":49},"01M6PVESM49C5NT7SB7N3F76VS","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.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fretro-to-framework\u002FSKILL.md",[191],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[193,194,195,196,159,197,198,199,164,116,42,34,200,97,201,202,203,204,205,206],"framework","retro","retro to framework","change","retrospective","projects","convert","across","problem","about","more","skill update","single","generic"]