[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGKM2QZK1CEWFPDDQWST19":3,"skill-same:01M6JGKM2QZK1CEWFPDDQWST19":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},"01M6JGKM2QZK1CEWFPDDQWST19","api-evolution-checklist",null,"Audit public-API\u002Fcontract changes against Hyrum, Tesler, Leaky Abstractions, and Lehman laws. Use when changing a public API signature, response shape, or error contract, refactoring a shared interface used by two or more callers, drafting an interface ADR, or reviewing a PR touching api\u002F, proto\u002F, or OpenAPI specs.","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\u002Fapi-evolution-checklist\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"checklist","api evolution checklist","evolution","api","shared","audit","changes","more","interface","public api","error","proto","contract","pr","shape","use","openapi","public","adr","refactoring","2026-11-10 10:12:30",false,"---\nname: api-evolution-checklist\ndescription: >-\n  Audit public-API\u002Fcontract changes against Hyrum, Tesler, Leaky\n  Abstractions, and Lehman laws. Use when changing a public API signature,\n  response shape, or error contract, refactoring a shared interface used\n  by two or more callers, drafting an interface ADR, or reviewing a PR\n  touching api\u002F, proto\u002F, or OpenAPI specs.\nlicense: MIT\n---\n# API Evolution Checklist\n\nVet a public-API or cross-component contract change against four laws that describe how interfaces decay over time.\n\n## When to Use\nSpecifically about the **compatibility** of a change to a shared\u002Fpublic\ninterface — what breaks downstream callers, how the contract decays over time.\nThe *decision record* for a versioning\u002Fdeprecation choice is **adr-manager**\n(this checklist often feeds one). Not for internal-only refactors with a single\ncaller — the cost is justified by ≥2 consumers of the surface.\n\n## Checklist\n\nFor each item: state the **assumption \u002F claim** and the **mitigation in place**. Mark `N\u002FA` only with explicit justification.\n\n1. **Hyrum's Law — observable behavior is a contract.**\n   List undocumented behaviors that callers may already depend on: timing\u002Flatency, error message text, ordering, retry semantics, optional-field defaults, idempotency, encoding edge cases. For each, decide: preserve, deprecate-with-window, or break-with-migration.\n2. **Tesler's Law — complexity is conserved, not eliminated.**\n   When the change \"simplifies\" the API, name where the removed complexity moved (caller code, runtime check, ops runbook, migration script). If you cannot point to it, the simplification is illusory.\n3. **Law of Leaky Abstractions — name the leaks.**\n   Document leak points the abstraction does NOT hide: error propagation, timeouts\u002Fcancellation, transactional boundaries, encoding\u002Flocale, performance cliffs. Make leaks part of the contract, not surprises.\n4. **Lehman's Laws — plan the next evolution, not just this one.**\n   Versioning scheme, deprecation window, sunset criteria, migration tooling, observability for old-vs-new traffic. A contract without an evolution plan freezes into legacy.\n\n## Completion\n- All 4 items have `assumption` + `mitigation` (or justified `N\u002FA`)\n- Findings appended to the API ADR or PR description\n- For breaking changes: deprecation window + migration path documented before merge\n\n## Example\nA team replaces `GET \u002Fusers?status=active` with `GET \u002Fusers` returning all users (filter via client). Hyrum: existing dashboards depend on the implicit \"active-only\" set — break-with-migration, not silent change. Tesler: filtering complexity moved to every caller — provide a client lib helper. Leaky: old endpoint streamed paginated; new one returns full list and OOMs at 100k users — keep pagination contract. Lehman: introduce `v2\u002Fusers` while `v1\u002Fusers` returns deprecation header; sunset after 2 release cycles.\n\n## Anti-Patterns\n- \"It's just a refactor, no contract change\" — if anyone outside this module calls it, it is a contract\n- Treating documentation as the contract — observable behavior outranks docs (Hyrum)\n- One-shot deprecation: removing without a window forces caller fire-drills\n- Hiding leaks behind nicer names instead of documenting them\n","# API Evolution Checklist\n\nVet a public-API or cross-component contract change against four laws that describe how interfaces decay over time.\n\n## When to Use\nSpecifically about the **compatibility** of a change to a shared\u002Fpublic\ninterface — what breaks downstream callers, how the contract decays over time.\nThe *decision record* for a versioning\u002Fdeprecation choice is **adr-manager**\n(this checklist often feeds one). Not for internal-only refactors with a single\ncaller — the cost is justified by ≥2 consumers of the surface.\n\n## Checklist\n\nFor each item: state the **assumption \u002F claim** and the **mitigation in place**. Mark `N\u002FA` only with explicit justification.\n\n1. **Hyrum's Law — observable behavior is a contract.**\n   List undocumented behaviors that callers may already depend on: timing\u002Flatency, error message text, ordering, retry semantics, optional-field defaults, idempotency, encoding edge cases. For each, decide: preserve, deprecate-with-window, or break-with-migration.\n2. **Tesler's Law — complexity is conserved, not eliminated.**\n   When the change \"simplifies\" the API, name where the removed complexity moved (caller code, runtime check, ops runbook, migration script). If you cannot point to it, the simplification is illusory.\n3. **Law of Leaky Abstractions — name the leaks.**\n   Document leak points the abstraction does NOT hide: error propagation, timeouts\u002Fcancellation, transactional boundaries, encoding\u002Flocale, performance cliffs. Make leaks part of the contract, not surprises.\n4. **Lehman's Laws — plan the next evolution, not just this one.**\n   Versioning scheme, deprecation window, sunset criteria, migration tooling, observability for old-vs-new traffic. A contract without an evolution plan freezes into legacy.\n\n## Completion\n- All 4 items have `assumption` + `mitigation` (or justified `N\u002FA`)\n- Findings appended to the API ADR or PR description\n- For breaking changes: deprecation window + migration path documented before merge\n\n## Example\nA team replaces `GET \u002Fusers?status=active` with `GET \u002Fusers` returning all users (filter via client). Hyrum: existing dashboards depend on the implicit \"active-only\" set — break-with-migration, not silent change. Tesler: filtering complexity moved to every caller — provide a client lib helper. Leaky: old endpoint streamed paginated; new one returns full list and OOMs at 100k users — keep pagination contract. Lehman: introduce `v2\u002Fusers` while `v1\u002Fusers` returns deprecation header; sunset after 2 release cycles.\n\n## Anti-Patterns\n- \"It's just a refactor, no contract change\" — if anyone outside this module calls it, it is a contract\n- Treating documentation as the contract — observable behavior outranks docs (Hyrum)\n- One-shot deprecation: removing without a window forces caller fire-drills\n- Hiding leaks behind nicer names instead of documenting them\n",{"name":5,"license":15,"description":7},"master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fapi-evolution-checklist",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 api-evolution-checklist",{"tool":67,"command":68},"bunx","bunx skills add muratovv\u002Fai-hats --skill api-evolution-checklist",{"tool":70,"command":71},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill api-evolution-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fapi-evolution-checklist\u002FSKILL.md",true,[],[76,102,126,147,170,184],{"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,44,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,44,118,119,120,121,122,39,123,124,125],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","with","bug-fix","phase",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"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",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,137,138,139,140,116,141,44,142,121,143,144,145,99,146],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"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",[153],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[155,156,157,158,159,160,34,161,162,163,44,164,165,166,167,168,169],"Optimization","skill optimization","components","component","issues","library","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"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",[],[177,178,179,180,181,182,44,183,99],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"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",[190],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,195,158,196,197,198,163,116,44,199,200,97,201,202,36,203,204,205],"framework","retro","retro to framework","change","retrospective","projects","convert","incident","across","problem","about","skill update","single","generic"]