[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-wondelai-release-it-zh-CN":3,"guides-for-wondelai-release-it":1281,"similar-k176y5akz2kkya8gd1dx7xt25986n1zg-zh-CN":1282},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":256,"isFallback":261,"parentExtension":262,"providers":323,"relations":327,"repo":328,"tags":1279,"workflow":1280},1778698867338.302,"k176y5akz2kkya8gd1dx7xt25986n1zg",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions \"production outage\", \"circuit breaker\", \"timeout strategy\", \"deployment pipeline\", \"chaos engineering\", \"bulkhead pattern\", \"retry with backoff\", or \"health checks\". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.",{"claudeCode":12},"wondelai/skills","Release It!","https://github.com/wondelai/skills",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":239,"workflow":254},1778699510092.1904,"kn75vc40zmdsa9xv55rtgv6zcn86ncrn","en",{"checks":20,"evaluatedAt":198,"extensionSummary":199,"features":200,"nonGoals":207,"practices":211,"prerequisites":217,"promptVersionExtension":218,"promptVersionScoring":219,"purpose":220,"rationale":221,"score":222,"summary":223,"tags":224,"targetMarket":231,"tier":232,"useCases":233},[21,26,29,32,36,39,43,46,50,54,58,61,64,68,72,76,80,84,87,91,94,97,100,103,106,109,113,116,120,124,128,131,134,137,141,144,147,150,153,156,159,163,167,170,173,177,180,182,184,186,188,190,192,194,196],{"category":22,"check":23,"severity":24,"summary":25},"Practical Utility","Problem relevance","pass","The description clearly states the problem of building production-ready systems with stability patterns and names specific use cases and triggers.",{"category":22,"check":27,"severity":24,"summary":28},"Unique selling proposition","The skill provides a structured framework based on well-known stability patterns and concepts, going beyond generic LLM advice.",{"category":22,"check":30,"severity":24,"summary":31},"Production readiness","The skill provides a comprehensive framework covering design principles, implementation patterns, and testing strategies for production systems.",{"category":33,"check":34,"severity":24,"summary":35},"Scope","Single responsibility principle","The skill focuses on a single domain: building production-ready, resilient software systems, with clear boundaries.",{"category":33,"check":37,"severity":24,"summary":38},"Description quality","The description accurately reflects the skill's content, is well-organized, and provides clear guidance on when to use it.",{"category":40,"check":41,"severity":24,"summary":42},"Invocation","Precise Purpose","The purpose is clearly defined by stating the artifact (production-ready systems) and the user intent (build with stability patterns, handle outages, design resilient microservices).",{"category":40,"check":44,"severity":24,"summary":45},"Concise Frontmatter","The frontmatter is concise, self-contained, and effectively summarizes the core capability and triggers.",{"category":47,"check":48,"severity":24,"summary":49},"Documentation","Concise Body","The main SKILL.md body is well-structured, uses progressive disclosure for deeper material, and stays within reasonable length.",{"category":51,"check":52,"severity":24,"summary":53},"Context","Progressive Disclosure","The SKILL.md effectively links to detailed reference files for specific topics like Chaos Engineering, Stability Patterns, etc., facilitating progressive disclosure.",{"category":51,"check":55,"severity":56,"summary":57},"Forked exploration","not_applicable","The skill does not appear to involve deep exploration or multi-file inspection requiring a forked context.",{"category":22,"check":59,"severity":24,"summary":60},"Usage examples","The skill includes example prompts that are ready-to-use and clearly demonstrate how to invoke the skill for various capabilities.",{"category":22,"check":62,"severity":24,"summary":63},"Edge cases","The reference files implicitly handle edge cases by detailing anti-patterns and failure modes, with recovery strategies discussed.",{"category":65,"check":66,"severity":56,"summary":67},"Code Execution","Tool Fallback","This skill appears to be a self-contained prompt-based tool and does not rely on external MCP servers or tools requiring fallbacks.",{"category":69,"check":70,"severity":24,"summary":71},"Safety","Halt on unexpected state","The principles discussed, particularly around chaos engineering and defensive programming, emphasize halting on unexpected states and graceful degradation.",{"category":73,"check":74,"severity":24,"summary":75},"Portability","Cross-skill coupling","The skill is self-contained and focuses on general principles, without requiring other specific skills to be loaded.",{"category":77,"check":78,"severity":24,"summary":79},"License","License usability","The extension uses the MIT license, which is a permissive open-source license, declared in a dedicated LICENSE file.",{"category":81,"check":82,"severity":24,"summary":83},"Maintenance","Commit recency","The last commit was on April 27, 2026, which is within the last 3 months.",{"category":81,"check":85,"severity":56,"summary":86},"Dependency Management","The extension does not appear to use any third-party dependencies that require explicit management.",{"category":88,"check":89,"severity":56,"summary":90},"Security","Secret Management","The skill does not handle secrets; it provides guidance and principles.",{"category":88,"check":92,"severity":24,"summary":93},"Injection","The skill focuses on design principles and patterns, not executing external code or loading untrusted data.",{"category":88,"check":95,"severity":24,"summary":96},"Transitive Supply-Chain Grenades","The skill does not fetch external content at runtime or execute arbitrary code.",{"category":88,"check":98,"severity":24,"summary":99},"Sandbox Isolation","The skill is informational and does not perform file system operations or interact with the sandbox in a way that could lead to escape.",{"category":88,"check":101,"severity":24,"summary":102},"Sandbox escape primitives","The skill is a prompt-based guide and does not contain scripts or instructions that could facilitate sandbox escapes.",{"category":88,"check":104,"severity":24,"summary":105},"Data Exfiltration","The skill is purely informational and does not make outbound calls or reference confidential data.",{"category":88,"check":107,"severity":24,"summary":108},"Hidden Text Tricks","The bundled content is free of hidden-steering tricks, with clean ASCII and expected Unicode in descriptions.",{"category":110,"check":111,"severity":24,"summary":112},"Hooks","Opaque code execution","The extension does not involve opaque code execution; all included content is readable markdown.",{"category":73,"check":114,"severity":56,"summary":115},"Structural Assumption","The skill provides guidance and does not make assumptions about user project structure.",{"category":117,"check":118,"severity":24,"summary":119},"Trust","Issues Attention","There are 0 open issues and 0 closed issues in the last 90 days, indicating low activity but not necessarily neglect given the skill's nature.",{"category":121,"check":122,"severity":24,"summary":123},"Versioning","Release Management","The SKILL.md frontmatter declares a meaningful semver version (1.1.0).",{"category":125,"check":126,"severity":56,"summary":127},"Execution","Validation","The skill is informational and does not execute code or process structured output that requires schema validation.",{"category":88,"check":129,"severity":56,"summary":130},"Unguarded Destructive Operations","The skill is informational and does not perform destructive operations.",{"category":65,"check":132,"severity":56,"summary":133},"Error Handling","The skill does not contain executable code that requires error handling.",{"category":65,"check":135,"severity":56,"summary":136},"Logging","The skill is informational and does not perform actions that require logging.",{"category":138,"check":139,"severity":56,"summary":140},"Compliance","GDPR","The skill does not operate on personal data.",{"category":138,"check":142,"severity":24,"summary":143},"Target market","The skill provides general principles applicable globally and does not exhibit any regional logic or restrictions.",{"category":73,"check":145,"severity":56,"summary":146},"Runtime stability","The skill is prompt-based and does not assume a specific runtime environment beyond the AI agent's capabilities.",{"category":47,"check":148,"severity":24,"summary":149},"README","The README file exists and clearly states the purpose of the skills repository, including installation instructions and a list of available skills.",{"category":33,"check":151,"severity":56,"summary":152},"Tool surface size","This is a single skill, not a collection of tools.",{"category":40,"check":154,"severity":56,"summary":155},"Overlapping near-synonym tools","This is a single skill and does not expose multiple tools.",{"category":47,"check":157,"severity":24,"summary":158},"Phantom features","All advertised capabilities align with the detailed content provided in the SKILL.md and reference files.",{"category":160,"check":161,"severity":24,"summary":162},"Install","Installation instruction","The README provides clear installation instructions for both Claude Code Plugin Marketplace and skills.sh, along with copy-paste examples.",{"category":164,"check":165,"severity":56,"summary":166},"Errors","Actionable error messages","The skill is informational and does not have user-facing error paths.",{"category":125,"check":168,"severity":56,"summary":169},"Pinned dependencies","The skill does not have dependencies that require pinning.",{"category":33,"check":171,"severity":56,"summary":172},"Dry-run preview","The skill is informational and does not perform state-changing operations.",{"category":174,"check":175,"severity":56,"summary":176},"Protocol","Idempotent retry & timeouts","The skill is informational and does not involve remote calls or state-changing operations.",{"category":138,"check":178,"severity":56,"summary":179},"Telemetry opt-in","The skill does not emit telemetry.",{"category":40,"check":44,"severity":24,"summary":181},"The frontmatter is dense and self-contained, providing a summary of core capabilities and trigger phrases within the recommended character limit.",{"category":47,"check":48,"severity":24,"summary":183},"The skill body is well-organized, delegates deeper material to reference files, and avoids unnecessary verbosity.",{"category":51,"check":52,"severity":24,"summary":185},"The SKILL.md references multiple `.md` files within a `references/` directory for detailed explanations, demonstrating effective progressive disclosure.",{"category":22,"check":59,"severity":24,"summary":187},"The skill provides multiple clear and ready-to-use example prompts for various capabilities, demonstrating practical application.",{"category":22,"check":62,"severity":24,"summary":189},"The reference documentation implicitly handles edge cases by discussing failure modes, anti-patterns, and prevention strategies.",{"category":47,"check":157,"severity":24,"summary":191},"All features and principles discussed in the documentation have corresponding explanations and are not phantom.",{"category":160,"check":161,"severity":24,"summary":193},"The README provides comprehensive installation instructions for multiple methods (Claude Code Marketplace, skills.sh) and includes detailed usage examples.",{"category":138,"check":142,"severity":24,"summary":195},"The skill provides general software engineering principles applicable globally, with no regional or jurisdictional limitations detected.",{"category":47,"check":148,"severity":24,"summary":197},"The README clearly outlines the purpose of the skills repository, provides installation instructions, and lists available skills with brief descriptions.",1778699509979,"This skill provides a structured framework and detailed guidance on building resilient, production-ready software systems, covering stability patterns, capacity planning, deployment strategies, and observability. It draws from established methodologies and books, offering principles, anti-patterns, and practical advice.",[201,202,203,204,205,206],"Explains stability anti-patterns and their countermeasures","Details essential stability patterns (circuit breakers, bulkheads, timeouts, retries)","Covers capacity planning and performance testing methodologies","Outlines safe deployment strategies (rolling, blue-green, canary, feature flags)","Guides on implementing observability (logs, metrics, traces, health checks)","Introduces chaos engineering principles and practices",[208,209,210],"Providing specific code implementations for every pattern","Replacing foundational books on system design and resilience","Automating chaos engineering experiments directly (guides on how to do it safely)",[212,213,214,215,216],"Stability Patterns","Capacity Planning","Deployment Strategies","Observability","Chaos Engineering",[],"3.0.0","4.4.0","To guide users in designing, deploying, and operating production-ready software systems that can withstand failures and operate reliably under real-world conditions.","Excellent documentation quality and practical utility, with clear purpose, features, and comprehensive reference materials. No critical or warning findings.",95,"A comprehensive and well-documented skill for building production-ready, resilient software systems.",[225,226,227,228,229,230],"resilience","production-readiness","system-design","chaos-engineering","stability-patterns","observability","global","verified",[234,235,236,237,238],"Designing resilient microservices","Planning zero-downtime deployments","Investigating cascading failure scenarios","Implementing capacity planning and health checks","Building systems that handle production outages gracefully",{"codeQuality":240,"collectedAt":242,"documentation":243,"maintenance":246,"security":251,"testCoverage":253},{"hasLockfile":241},false,1778699497516,{"descriptionLength":244,"readmeSize":245},589,84906,{"closedIssues90d":8,"forks":247,"hasChangelog":241,"manifestVersion":248,"openIssues90d":8,"pushedAt":249,"stars":250},110,"1.1.0",1777303489000,953,{"hasNpmPackage":241,"license":252,"smitheryVerified":241},"MIT",{"hasCi":241,"hasTests":241},{"updatedAt":255},1778699510092,{"basePath":257,"githubOwner":258,"githubRepo":259,"locale":18,"slug":257,"type":260},"release-it","wondelai","skills","skill",true,{"_creationTime":263,"_id":264,"community":265,"display":266,"identity":270,"parentExtension":273,"providers":307,"relations":319,"tags":320,"workflow":321},1778698867338.2917,"k17bj16z8e1yp2wwfd2hxagjtd86m0fp",{"reviewCount":8},{"description":267,"installMethods":268,"name":269,"sourceUrl":14},"Product strategy and innovation frameworks including Jobs to Be Done (Clayton Christensen) for customer discovery and product design, plus tactical negotiation skills (Chris Voss)",{"claudeCode":259},"Wondel.ai Skills",{"basePath":271,"githubOwner":258,"githubRepo":259,"locale":18,"slug":259,"type":272},"","plugin",{"_creationTime":274,"_id":275,"community":276,"display":277,"identity":281,"providers":283,"relations":301,"tags":303,"workflow":304},1778698867338.2915,"k17b5xtbnc3ma310pdjq42f8w186m4n1",{"reviewCount":8},{"description":278,"installMethods":279,"name":280,"sourceUrl":14},"42 agent skills for product strategy, UX design, marketing, sales, motivation, conversion optimization, code quality, and systems architecture — based on bestselling books",{"claudeCode":12},"wondelai-skills",{"basePath":271,"githubOwner":258,"githubRepo":259,"locale":18,"slug":259,"type":282},"marketplace",{"evaluate":284,"extract":295},{"promptVersionExtension":285,"promptVersionScoring":219,"score":286,"tags":287,"targetMarket":231,"tier":232},"3.1.0",99,[282,288,289,290,291,292,293,294],"curation","business-strategy","product-development","ux-design","marketing","sales","code-quality",{"commitSha":296,"marketplace":297,"plugin":299},"HEAD",{"name":280,"pluginCount":298},1,{"mcpCount":8,"provider":300,"skillCount":8},"classify",{"repoId":302},"kd7aexggvp8qjwjtgjbetg0jch86mg5a",[289,294,288,292,282,290,293,291],{"evaluatedAt":305,"extractAt":306,"updatedAt":305},1778698884072,1778698867338,{"evaluate":308,"extract":316},{"promptVersionExtension":218,"promptVersionScoring":219,"score":309,"tags":310,"targetMarket":231,"tier":232},98,[311,312,313,314,315],"systems-architecture","distributed-systems","software-design","technical-books","knowledge-base",{"commitSha":296,"license":252,"plugin":317},{"mcpCount":8,"provider":300,"skillCount":318},43,{"parentExtensionId":275,"repoId":302},[312,315,313,311,314],{"evaluatedAt":322,"extractAt":306,"updatedAt":322},1778699016780,{"evaluate":324,"extract":326},{"promptVersionExtension":218,"promptVersionScoring":219,"score":222,"tags":325,"targetMarket":231,"tier":232},[225,226,227,228,229,230],{"commitSha":296,"license":252},{"parentExtensionId":264,"repoId":302},{"_creationTime":329,"_id":302,"identity":330,"providers":331,"workflow":1275},1778698861437.7021,{"githubOwner":258,"githubRepo":259,"sourceUrl":14},{"classify":332,"discover":1258,"github":1261},{"commitSha":296,"extensions":333},[334,347,354,360,367,374,381,388,395,402,408,431,454,473,492,516,534,553,575,596,622,646,665,685,704,723,749,768,794,812,841,857,884,902,925,943,961,970,992,1019,1038,1059,1078,1095,1112,1127,1146,1165,1182,1197,1220,1241],{"basePath":271,"description":278,"displayName":280,"installMethods":335,"rationale":336,"selectedPaths":337,"source":346,"sourceLanguage":18,"type":282},{"claudeCode":12},"marketplace.json at .claude-plugin/marketplace.json",[338,341,343],{"path":339,"priority":340},".claude-plugin/marketplace.json","mandatory",{"path":342,"priority":340},"README.md",{"path":344,"priority":345},"LICENSE","high","rule",{"basePath":271,"description":267,"displayName":348,"installMethods":349,"rationale":350,"selectedPaths":351,"source":346,"sourceLanguage":18,"type":272},"product-strategy",{"claudeCode":259},"inline plugin source from marketplace.json at /",[352,353],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":355,"displayName":291,"installMethods":356,"rationale":350,"selectedPaths":357,"source":346,"sourceLanguage":18,"type":272},"UX and UI design skills including Refactoring UI, iOS HIG design, usability heuristics, habit-forming product design, behavior design for retention, web typography, award-winning top-design, and Don Norman's foundational design principles",{"claudeCode":259},[358,359],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":361,"displayName":362,"installMethods":363,"rationale":350,"selectedPaths":364,"source":346,"sourceLanguage":18,"type":272},"Marketing and conversion optimization skills including CRO methodology, StoryBrand messaging, Scorecard Marketing lead generation, viral marketing (Contagious), and 1-Page Marketing Plan","marketing-cro",{"claudeCode":259},[365,366],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":368,"displayName":369,"installMethods":370,"rationale":350,"selectedPaths":371,"source":346,"sourceLanguage":18,"type":272},"Sales, persuasion, and messaging skills including Cialdini's influence psychology, Aaron Ross's outbound sales methodology, Heath Brothers' sticky messaging, and Alex Hormozi's offer creation","sales-influence",{"claudeCode":259},[372,373],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":375,"displayName":376,"installMethods":377,"rationale":350,"selectedPaths":378,"source":346,"sourceLanguage":18,"type":272},"Product innovation and validation frameworks including Lean Startup methodology, Google Ventures Design Sprint, and Don Norman's design principles","product-innovation",{"claudeCode":259},[379,380],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":382,"displayName":383,"installMethods":384,"rationale":350,"selectedPaths":385,"source":346,"sourceLanguage":18,"type":272},"Business strategy and growth frameworks including Crossing the Chasm tech adoption, Blue Ocean Strategy value innovation, EOS business operating system, and Obviously Awesome positioning","strategy-growth",{"claudeCode":259},[386,387],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":389,"displayName":390,"installMethods":391,"rationale":350,"selectedPaths":392,"source":346,"sourceLanguage":18,"type":272},"Team motivation and intrinsic drive framework based on Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles for designing engaging products and teams","team-motivation",{"claudeCode":259},[393,394],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":396,"displayName":397,"installMethods":398,"rationale":350,"selectedPaths":399,"source":346,"sourceLanguage":18,"type":272},"Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), and Domain-Driven Design (Eric Evans)","code-craftsmanship",{"claudeCode":259},[400,401],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":271,"description":403,"displayName":311,"installMethods":404,"rationale":350,"selectedPaths":405,"source":346,"sourceLanguage":18,"type":272},"Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), and High Performance Browser Networking (Ilya Grigorik)",{"claudeCode":259},[406,407],{"path":342,"priority":340},{"path":344,"priority":345},{"basePath":409,"description":410,"displayName":409,"installMethods":411,"rationale":412,"selectedPaths":413,"source":346,"sourceLanguage":18,"type":260},"37signals-way","Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions \"Getting Real\", \"Rework\", \"Shape Up\", \"37signals\", \"Basecamp method\", \"six-week cycles\", \"fixed time variable scope\", \"appetite vs estimates\", \"betting table\", \"breadboarding\", \"fat marker sketch\", \"build less\", \"underdo the competition\", or \"opinionated software\". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.",{"claudeCode":12},"SKILL.md frontmatter at 37signals-way/SKILL.md",[414,416,419,421,423,425,427,429],{"path":415,"priority":340},"SKILL.md",{"path":417,"priority":418},"references/betting-cycles.md","medium",{"path":420,"priority":418},"references/build-less.md",{"path":422,"priority":418},"references/case-studies.md",{"path":424,"priority":418},"references/opinionated-software.md",{"path":426,"priority":418},"references/shaping-work.md",{"path":428,"priority":418},"references/small-teams-execution.md",{"path":430,"priority":418},"references/ux-ui-copy.md",{"basePath":432,"description":433,"displayName":432,"installMethods":434,"rationale":435,"selectedPaths":436,"source":346,"sourceLanguage":18,"type":260},"blue-ocean-strategy","Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions \"blue ocean\", \"red ocean\", \"strategy canvas\", \"ERRC framework\", \"value innovation\", \"non-customers\", \"buyer utility map\", \"eliminate-reduce-raise-create\", or \"uncontested market\". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.",{"claudeCode":12},"SKILL.md frontmatter at blue-ocean-strategy/SKILL.md",[437,438,440,442,444,446,448,450,452],{"path":415,"priority":340},{"path":439,"priority":418},"references/blue-ocean-examples.md",{"path":441,"priority":418},"references/errc-grid.md",{"path":443,"priority":418},"references/implementation.md",{"path":445,"priority":418},"references/non-customers.md",{"path":447,"priority":418},"references/sequence.md",{"path":449,"priority":418},"references/six-paths.md",{"path":451,"priority":418},"references/strategy-canvas.md",{"path":453,"priority":418},"references/value-innovation.md",{"basePath":455,"description":456,"displayName":455,"installMethods":457,"rationale":458,"selectedPaths":459,"source":346,"sourceLanguage":18,"type":260},"clean-architecture","Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions \"architecture layers\", \"dependency rule\", \"ports and adapters\", \"hexagonal architecture\", \"use case boundary\", \"onion architecture\", \"screaming architecture\", or \"framework independence\". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.",{"claudeCode":12},"SKILL.md frontmatter at clean-architecture/SKILL.md",[460,461,463,465,467,469,471],{"path":415,"priority":340},{"path":462,"priority":418},"references/adapters-frameworks.md",{"path":464,"priority":418},"references/boundaries.md",{"path":466,"priority":418},"references/component-principles.md",{"path":468,"priority":418},"references/dependency-rule.md",{"path":470,"priority":418},"references/entities-use-cases.md",{"path":472,"priority":418},"references/solid-principles.md",{"basePath":474,"description":475,"displayName":474,"installMethods":476,"rationale":477,"selectedPaths":478,"source":346,"sourceLanguage":18,"type":260},"clean-code","Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions \"code review\", \"naming conventions\", \"function too long\", \"code smells\", \"readable code\", \"boy scout rule\", \"single responsibility\", or \"unit test quality\". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.",{"claudeCode":12},"SKILL.md frontmatter at clean-code/SKILL.md",[479,480,482,484,486,488,490],{"path":415,"priority":340},{"path":481,"priority":418},"references/code-smells.md",{"path":483,"priority":418},"references/comments-formatting.md",{"path":485,"priority":418},"references/error-handling.md",{"path":487,"priority":418},"references/functions-and-methods.md",{"path":489,"priority":418},"references/naming-conventions.md",{"path":491,"priority":418},"references/testing-principles.md",{"basePath":493,"description":494,"displayName":493,"installMethods":495,"rationale":496,"selectedPaths":497,"source":346,"sourceLanguage":18,"type":260},"contagious","Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions \"go viral\", \"word of mouth\", \"shareable content\", \"social currency\", \"why people share\", \"viral loop\", \"referral program\", or \"organic growth\". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.",{"claudeCode":12},"SKILL.md frontmatter at contagious/SKILL.md",[498,499,500,502,504,506,508,510,512,514],{"path":415,"priority":340},{"path":422,"priority":418},{"path":501,"priority":418},"references/emotion.md",{"path":503,"priority":418},"references/practical-value.md",{"path":505,"priority":418},"references/public-visibility.md",{"path":507,"priority":418},"references/social-currency.md",{"path":509,"priority":418},"references/stories-trojan-horse.md",{"path":511,"priority":418},"references/triggers.md",{"path":513,"priority":418},"references/viral-content-patterns.md",{"path":515,"priority":418},"references/word-of-mouth.md",{"basePath":517,"description":518,"displayName":517,"installMethods":519,"rationale":520,"selectedPaths":521,"source":346,"sourceLanguage":18,"type":260},"continuous-discovery","Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions \"continuous discovery\", \"opportunity solution tree\", \"weekly interviews\", \"assumption testing\", \"discovery habits\", \"product trio\", or \"outcome-based roadmap\". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.",{"claudeCode":12},"SKILL.md frontmatter at continuous-discovery/SKILL.md",[522,523,525,526,528,530,532],{"path":415,"priority":340},{"path":524,"priority":418},"references/assumption-mapping.md",{"path":422,"priority":418},{"path":527,"priority":418},"references/experience-mapping.md",{"path":529,"priority":418},"references/interview-snapshots.md",{"path":531,"priority":418},"references/opportunity-trees.md",{"path":533,"priority":418},"references/prioritization-methods.md",{"basePath":535,"description":536,"displayName":535,"installMethods":537,"rationale":538,"selectedPaths":539,"source":346,"sourceLanguage":18,"type":260},"cro-methodology","Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions \"landing page isnt converting\", \"conversion rate\", \"A/B test\", \"why visitors leave\", \"objection handling\", \"bounce rate\", \"split testing\", or \"conversion funnel\". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.",{"claudeCode":12},"SKILL.md frontmatter at cro-methodology/SKILL.md",[540,541,543,545,547,549,551],{"path":415,"priority":340},{"path":542,"priority":418},"references/COPYWRITING.md",{"path":544,"priority":418},"references/OBJECTIONS.md",{"path":546,"priority":418},"references/PERSUASION.md",{"path":548,"priority":418},"references/RESEARCH.md",{"path":550,"priority":418},"references/funnel-analysis.md",{"path":552,"priority":418},"references/testing-methodology.md",{"basePath":554,"description":555,"displayName":554,"installMethods":556,"rationale":557,"selectedPaths":558,"source":346,"sourceLanguage":18,"type":260},"crossing-the-chasm","Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions \"crossing the chasm\", \"beachhead segment\", \"whole product\", \"early adopters vs. mainstream\", \"tech go-to-market\", \"bowling pin strategy\", \"technology adoption lifecycle\", or \"pragmatist buyers\". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.",{"claudeCode":12},"SKILL.md frontmatter at crossing-the-chasm/SKILL.md",[559,560,562,564,566,567,569,571,573],{"path":415,"priority":340},{"path":561,"priority":418},"references/b2b-saas.md",{"path":563,"priority":418},"references/beachhead-selection.md",{"path":565,"priority":418},"references/buyer-segments.md",{"path":422,"priority":418},{"path":568,"priority":418},"references/expansion.md",{"path":570,"priority":418},"references/go-to-market.md",{"path":572,"priority":418},"references/positioning.md",{"path":574,"priority":418},"references/whole-product.md",{"basePath":576,"description":577,"displayName":576,"installMethods":578,"rationale":579,"selectedPaths":580,"source":346,"sourceLanguage":18,"type":260},"ddia-systems","Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions \"database choice\", \"replication lag\", \"partitioning strategy\", \"consistency vs availability\", \"stream processing\", \"ACID transactions\", \"eventual consistency\", or \"LSM tree vs B-tree\". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.",{"claudeCode":12},"SKILL.md frontmatter at ddia-systems/SKILL.md",[581,582,584,586,588,590,592,594],{"path":415,"priority":340},{"path":583,"priority":418},"references/batch-stream.md",{"path":585,"priority":418},"references/data-models.md",{"path":587,"priority":418},"references/fault-tolerance.md",{"path":589,"priority":418},"references/partitioning.md",{"path":591,"priority":418},"references/replication.md",{"path":593,"priority":418},"references/storage-engines.md",{"path":595,"priority":418},"references/transactions.md",{"basePath":597,"description":598,"displayName":597,"installMethods":599,"rationale":600,"selectedPaths":601,"source":346,"sourceLanguage":18,"type":260},"design-everyday-things","Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions \"why is this confusing\", \"affordance\", \"error prevention\", \"discoverability\", \"human-centered design\", \"fault tolerance\", \"mental model\", \"mapping\", or \"seven stages of action\". Also trigger when diagnosing why users make mistakes, reducing product complexity, or improving error messages and feedback systems. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.",{"claudeCode":12},"SKILL.md frontmatter at design-everyday-things/SKILL.md",[602,603,605,606,608,610,612,614,616,618,620],{"path":415,"priority":340},{"path":604,"priority":418},"references/affordances.md",{"path":422,"priority":418},{"path":607,"priority":418},"references/conceptual-models.md",{"path":609,"priority":418},"references/constraints.md",{"path":611,"priority":418},"references/feedback.md",{"path":613,"priority":418},"references/human-error.md",{"path":615,"priority":418},"references/mappings.md",{"path":617,"priority":418},"references/seven-stages.md",{"path":619,"priority":418},"references/signifiers.md",{"path":621,"priority":418},"references/two-gulfs.md",{"basePath":623,"description":624,"displayName":623,"installMethods":625,"rationale":626,"selectedPaths":627,"source":346,"sourceLanguage":18,"type":260},"design-sprint","Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions \"design sprint\", \"validate in a week\", \"rapid prototype\", \"test with users\", \"de-risk before building\", \"GV sprint\", \"prototype testing\", or \"design workshop\". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.",{"claudeCode":12},"SKILL.md frontmatter at design-sprint/SKILL.md",[628,629,630,632,634,636,638,640,642,644],{"path":415,"priority":340},{"path":422,"priority":418},{"path":631,"priority":418},"references/facilitation.md",{"path":633,"priority":418},"references/friday.md",{"path":635,"priority":418},"references/monday.md",{"path":637,"priority":418},"references/recruiting.md",{"path":639,"priority":418},"references/remote-sprints.md",{"path":641,"priority":418},"references/thursday.md",{"path":643,"priority":418},"references/tuesday.md",{"path":645,"priority":418},"references/wednesday.md",{"basePath":647,"description":648,"displayName":647,"installMethods":649,"rationale":650,"selectedPaths":651,"source":346,"sourceLanguage":18,"type":260},"domain-driven-design","Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions \"domain modeling\", \"bounded context\", \"aggregate root\", \"ubiquitous language\", \"anti-corruption layer\", \"context mapping\", \"domain events\", or \"strategic design\". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.",{"claudeCode":12},"SKILL.md frontmatter at domain-driven-design/SKILL.md",[652,653,655,657,659,661,663],{"path":415,"priority":340},{"path":654,"priority":418},"references/bounded-contexts.md",{"path":656,"priority":418},"references/building-blocks.md",{"path":658,"priority":418},"references/domain-events.md",{"path":660,"priority":418},"references/repositories-factories.md",{"path":662,"priority":418},"references/strategic-design.md",{"path":664,"priority":418},"references/ubiquitous-language.md",{"basePath":666,"description":667,"displayName":666,"installMethods":668,"rationale":669,"selectedPaths":670,"source":346,"sourceLanguage":18,"type":260},"drive-motivation","Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions \"intrinsic motivation\", \"gamification isnt working\", \"team incentives\", \"autonomy\", \"mastery\", \"purpose-driven\", \"employee engagement\", or \"reward systems\". Also trigger when designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.",{"claudeCode":12},"SKILL.md frontmatter at drive-motivation/SKILL.md",[671,672,674,676,677,679,681,683],{"path":415,"priority":340},{"path":673,"priority":418},"references/applications.md",{"path":675,"priority":418},"references/autonomy.md",{"path":422,"priority":418},{"path":678,"priority":418},"references/extrinsic-rewards.md",{"path":680,"priority":418},"references/mastery.md",{"path":682,"priority":418},"references/purpose.md",{"path":684,"priority":418},"references/type-i.md",{"basePath":686,"description":687,"displayName":686,"installMethods":688,"rationale":689,"selectedPaths":690,"source":346,"sourceLanguage":18,"type":260},"high-perf-browser","Optimize web performance through network protocols, resource loading, and browser rendering internals. Use when the user mentions \"page load speed\", \"Core Web Vitals\", \"HTTP/2\", \"resource hints\", \"network latency\", \"render blocking\", \"TCP optimization\", \"service worker\", or \"critical rendering path\". Also trigger when diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes. Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection. For UI visual performance, see refactoring-ui. For font loading, see web-typography.",{"claudeCode":12},"SKILL.md frontmatter at high-perf-browser/SKILL.md",[691,692,694,696,698,700,702],{"path":415,"priority":340},{"path":693,"priority":418},"references/caching-strategies.md",{"path":695,"priority":418},"references/core-web-vitals.md",{"path":697,"priority":418},"references/http-protocols.md",{"path":699,"priority":418},"references/network-fundamentals.md",{"path":701,"priority":418},"references/real-time-communication.md",{"path":703,"priority":418},"references/resource-loading.md",{"basePath":705,"description":706,"displayName":705,"installMethods":707,"rationale":708,"selectedPaths":709,"source":346,"sourceLanguage":18,"type":260},"hooked-ux","Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions \"users arent coming back\", \"engagement loops\", \"habit formation\", \"push notifications\", \"variable rewards\", \"daily active users\", \"habit zone\", or \"user retention loops\". Also trigger when designing notification strategies, building streaks or progress systems, or analyzing why users stop using a product after initial signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.",{"claudeCode":12},"SKILL.md frontmatter at hooked-ux/SKILL.md",[710,711,712,714,716,718,720,722],{"path":415,"priority":340},{"path":422,"priority":418},{"path":713,"priority":418},"references/ethical-boundaries.md",{"path":715,"priority":418},"references/habit-testing.md",{"path":717,"priority":418},"references/neuroscience-foundations.md",{"path":719,"priority":418},"references/product-applications.md",{"path":721,"priority":418},"references/rewards.md",{"path":511,"priority":418},{"basePath":724,"description":725,"displayName":724,"installMethods":726,"rationale":727,"selectedPaths":728,"source":346,"sourceLanguage":18,"type":260},"hundred-million-offers","Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions \"pricing strategy\", \"irresistible offer\", \"bonuses and guarantees\", \"value-to-price ratio\", \"offer naming\", \"grand slam offer\", \"guarantee strategy\", or \"premium pricing justification\". Also trigger when packaging products for higher perceived value, designing money-back guarantees, or structuring pricing tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.",{"claudeCode":12},"SKILL.md frontmatter at hundred-million-offers/SKILL.md",[729,730,732,733,735,737,739,741,743,745,747],{"path":415,"priority":340},{"path":731,"priority":418},"references/bonuses-stacking.md",{"path":422,"priority":418},{"path":734,"priority":418},"references/grand-slam-offers.md",{"path":736,"priority":418},"references/guarantees.md",{"path":738,"priority":418},"references/naming-offers.md",{"path":740,"priority":418},"references/offer-creation-checklist.md",{"path":742,"priority":418},"references/pricing-strategy.md",{"path":744,"priority":418},"references/scarcity-urgency.md",{"path":746,"priority":418},"references/starving-crowd.md",{"path":748,"priority":418},"references/value-equation.md",{"basePath":750,"description":751,"displayName":750,"installMethods":752,"rationale":753,"selectedPaths":754,"source":346,"sourceLanguage":18,"type":260},"improve-retention","Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions \"users drop off\", \"activation rate\", \"onboarding friction\", \"retention metrics\", \"why users dont complete\", \"churn analysis\", \"user activation\", or \"aha moment\". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.",{"claudeCode":12},"SKILL.md frontmatter at improve-retention/SKILL.md",[755,756,758,760,761,763,764,766],{"path":415,"priority":340},{"path":757,"priority":418},"references/ability-chain.md",{"path":759,"priority":418},"references/behavior-model.md",{"path":422,"priority":418},{"path":762,"priority":418},"references/motivation-waves.md",{"path":719,"priority":418},{"path":765,"priority":418},"references/prompt-design.md",{"path":767,"priority":418},"references/tiny-habits.md",{"basePath":769,"description":770,"displayName":769,"installMethods":771,"rationale":772,"selectedPaths":773,"source":346,"sourceLanguage":18,"type":260},"influence-psychology","Apply the six principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity) to product design, copy, and sales. Use when the user mentions \"social proof\", \"persuasive copy\", \"why users dont convert\", \"ethical persuasion\", \"reciprocity\", \"scarcity tactics\", or \"commitment and consistency\". Also trigger when designing testimonial sections, crafting urgency messaging, or improving trust signals on landing pages. For deal negotiation tactics, see negotiation. For viral word-of-mouth, see contagious.",{"claudeCode":12},"SKILL.md frontmatter at influence-psychology/SKILL.md",[774,775,777,778,780,782,784,786,788,790,792],{"path":415,"priority":340},{"path":776,"priority":418},"references/authority.md",{"path":422,"priority":418},{"path":779,"priority":418},"references/commitment-consistency.md",{"path":781,"priority":418},"references/copywriting.md",{"path":783,"priority":418},"references/ethics.md",{"path":785,"priority":418},"references/liking.md",{"path":787,"priority":418},"references/reciprocity.md",{"path":789,"priority":418},"references/scarcity.md",{"path":791,"priority":418},"references/social-proof.md",{"path":793,"priority":418},"references/unity.md",{"basePath":795,"description":796,"displayName":795,"installMethods":797,"rationale":798,"selectedPaths":799,"source":346,"sourceLanguage":18,"type":260},"inspired-product","Build empowered product teams using discovery and delivery dual-track. Use when the user mentions \"product discovery\", \"empowered teams\", \"feature factory\", \"product roadmap\", \"opportunity assessment\", \"product vision\", \"product-led growth\", or \"discovery vs delivery\". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.",{"claudeCode":12},"SKILL.md frontmatter at inspired-product/SKILL.md",[800,801,802,804,806,808,810],{"path":415,"priority":340},{"path":422,"priority":418},{"path":803,"priority":418},"references/discovery-techniques.md",{"path":805,"priority":418},"references/empowered-teams.md",{"path":807,"priority":418},"references/opportunity-assessment.md",{"path":809,"priority":418},"references/product-vision.md",{"path":811,"priority":418},"references/stakeholder-management.md",{"basePath":813,"description":814,"displayName":813,"installMethods":815,"rationale":816,"selectedPaths":817,"source":346,"sourceLanguage":18,"type":260},"ios-hig-design","Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions \"iPhone app\", \"iPad layout\", \"SwiftUI\", \"UIKit\", \"Dynamic Island\", \"safe areas\", \"HIG compliance\", \"SF Symbols\", \"haptic feedback\", or \"iOS accessibility\". Also trigger when building tab bars, navigation stacks, sheets, or modals for iOS, implementing dark mode, or adapting layouts for different screen sizes. Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.",{"claudeCode":12},"SKILL.md frontmatter at ios-hig-design/SKILL.md",[818,819,821,823,825,827,829,831,833,835,837,839],{"path":415,"priority":340},{"path":820,"priority":418},"references/accessibility.md",{"path":822,"priority":418},"references/app-icons.md",{"path":824,"priority":418},"references/colors-depth.md",{"path":826,"priority":418},"references/components.md",{"path":828,"priority":418},"references/gestures.md",{"path":830,"priority":418},"references/keyboard-input.md",{"path":832,"priority":418},"references/navigation.md",{"path":834,"priority":418},"references/privacy-permissions.md",{"path":836,"priority":418},"references/system-integration.md",{"path":838,"priority":418},"references/typography.md",{"path":840,"priority":418},"references/widgets-extensions.md",{"basePath":842,"description":843,"displayName":842,"installMethods":844,"rationale":845,"selectedPaths":846,"source":346,"sourceLanguage":18,"type":260},"jobs-to-be-done","Discover what customers truly need by analyzing the \"job\" they hire your product to do. Use when the user mentions \"customer discovery\", \"why customers churn\", \"what job does this solve\", \"competing against luck\", \"product-market fit\", \"switching behavior\", \"milkshake moment\", or \"functional vs emotional jobs\". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing product value propositions. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint.",{"claudeCode":12},"SKILL.md frontmatter at jobs-to-be-done/SKILL.md",[847,848,849,851,853,855],{"path":415,"priority":340},{"path":422,"priority":418},{"path":850,"priority":418},"references/competitive-strategy.md",{"path":852,"priority":418},"references/diagnostics.md",{"path":854,"priority":418},"references/innovation-process.md",{"path":856,"priority":418},"references/organizational-change.md",{"basePath":858,"description":859,"displayName":858,"installMethods":860,"rationale":861,"selectedPaths":862,"source":346,"sourceLanguage":18,"type":260},"lean-startup","Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions \"MVP scope\", \"validated learning\", \"pivot or persevere\", \"vanity metrics\", \"test assumptions\", \"innovation accounting\", \"build-measure-learn\", or \"minimum viable experiment\". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.",{"claudeCode":12},"SKILL.md frontmatter at lean-startup/SKILL.md",[863,864,865,867,869,870,872,874,876,878,880,882],{"path":415,"priority":340},{"path":673,"priority":418},{"path":866,"priority":418},"references/assumptions.md",{"path":868,"priority":418},"references/build-measure-learn.md",{"path":422,"priority":418},{"path":871,"priority":418},"references/five-whys.md",{"path":873,"priority":418},"references/growth-engines.md",{"path":875,"priority":418},"references/innovation-accounting.md",{"path":877,"priority":418},"references/metrics.md",{"path":879,"priority":418},"references/mvp-design.md",{"path":881,"priority":418},"references/pivots.md",{"path":883,"priority":418},"references/small-batches.md",{"basePath":885,"description":886,"displayName":885,"installMethods":887,"rationale":888,"selectedPaths":889,"source":346,"sourceLanguage":18,"type":260},"lean-ux","Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions \"Lean UX\", \"design hypothesis\", \"UX experiment\", \"collaborative design\", \"outcome over output\", \"design studio method\", \"assumption mapping\", or \"lightweight research\". Also trigger when reducing design documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.",{"claudeCode":12},"SKILL.md frontmatter at lean-ux/SKILL.md",[890,891,893,894,896,898,900],{"path":415,"priority":340},{"path":892,"priority":418},"references/agile-integration.md",{"path":422,"priority":418},{"path":895,"priority":418},"references/collaborative-design.md",{"path":897,"priority":418},"references/experiment-patterns.md",{"path":899,"priority":418},"references/hypothesis-canvas.md",{"path":901,"priority":418},"references/outcome-metrics.md",{"basePath":903,"description":904,"displayName":903,"installMethods":905,"rationale":906,"selectedPaths":907,"source":346,"sourceLanguage":18,"type":260},"made-to-stick","Craft messages that are understood, remembered, and drive action using the SUCCESs checklist (Simple, Unexpected, Concrete, Credible, Emotional, Stories). Use when the user mentions \"make it memorable\", \"sticky messaging\", \"tagline\", \"value proposition\", \"why the message isnt landing\", \"knowledge curse\", \"surprise gap\", or \"concrete language\". Also trigger when writing pitch decks, simplifying complex product explanations, or making presentations more compelling and memorable. For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious.",{"claudeCode":12},"SKILL.md frontmatter at made-to-stick/SKILL.md",[908,909,910,911,913,915,917,919,921,923],{"path":415,"priority":340},{"path":673,"priority":418},{"path":422,"priority":418},{"path":912,"priority":418},"references/concrete.md",{"path":914,"priority":418},"references/credible.md",{"path":916,"priority":418},"references/curse-of-knowledge.md",{"path":918,"priority":418},"references/emotional.md",{"path":920,"priority":418},"references/simple.md",{"path":922,"priority":418},"references/stories.md",{"path":924,"priority":418},"references/unexpected.md",{"basePath":926,"description":927,"displayName":926,"installMethods":928,"rationale":929,"selectedPaths":930,"source":346,"sourceLanguage":18,"type":260},"microinteractions","Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions \"microinteraction\", \"button feedback\", \"loading state\", \"toggle design\", \"animation detail\", \"interaction polish\", \"state transitions\", or \"input feedback\". Also trigger when designing form validation responses, progress indicators, confirmation dialogs, or any UI element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.",{"claudeCode":12},"SKILL.md frontmatter at microinteractions/SKILL.md",[931,932,933,935,937,939,941],{"path":415,"priority":340},{"path":422,"priority":418},{"path":934,"priority":418},"references/feedback-patterns.md",{"path":936,"priority":418},"references/loops-modes.md",{"path":938,"priority":418},"references/rules-and-state.md",{"path":940,"priority":418},"references/signature-moments.md",{"path":942,"priority":418},"references/trigger-design.md",{"basePath":944,"description":945,"displayName":944,"installMethods":946,"rationale":947,"selectedPaths":948,"source":346,"sourceLanguage":18,"type":260},"mom-test","Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions \"customer interviews\", \"validate my idea\", \"users say they want it but dont buy\", \"leading questions\", \"The Mom Test\", \"customer feedback bias\", or \"interview script\". Also trigger when preparing user research questions, interpreting ambiguous customer feedback, or designing customer discovery processes that avoid false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.",{"claudeCode":12},"SKILL.md frontmatter at mom-test/SKILL.md",[949,950,952,953,955,957,959],{"path":415,"priority":340},{"path":951,"priority":418},"references/avoiding-bad-data.md",{"path":422,"priority":418},{"path":954,"priority":418},"references/commitment-advancement.md",{"path":956,"priority":418},"references/finding-conversations.md",{"path":958,"priority":418},"references/processing-learning.md",{"path":960,"priority":418},"references/question-patterns.md",{"basePath":962,"description":963,"displayName":962,"installMethods":964,"rationale":965,"selectedPaths":966,"source":346,"sourceLanguage":18,"type":260},"negotiation","Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions \"salary negotiation\", \"contract terms\", \"handling objections\", \"mirroring and labeling\", \"difficult conversation\", \"deal terms\", \"BATNA\", or \"anchoring\". Also trigger when preparing for vendor negotiations, resolving pricing disputes, or navigating high-stakes conversations where both parties need to feel heard. Covers accusation audits, Black Swan discovery, and the \"Thats Right\" technique. For persuasion in product/marketing, see influence-psychology.",{"claudeCode":12},"SKILL.md frontmatter at negotiation/SKILL.md",[967,968],{"path":415,"priority":340},{"path":969,"priority":418},"references/techniques.md",{"basePath":971,"description":972,"displayName":971,"installMethods":973,"rationale":974,"selectedPaths":975,"source":346,"sourceLanguage":18,"type":260},"obviously-awesome","Define product positioning by mapping competitive alternatives, unique attributes, and best-fit customers to the right market category. Use when the user mentions \"positioning\", \"competitive alternatives\", \"how to position\", \"market category\", \"why customers dont get it\", \"positioning canvas\", \"repositioning\", or \"category creation\". Also trigger when launching a new product, entering a crowded market, or diagnosing why prospects dont understand the products value. Covers positioning canvas and team workshops. For customer jobs analysis, see jobs-to-be-done. For go-to-market, see crossing-the-chasm.",{"claudeCode":12},"SKILL.md frontmatter at obviously-awesome/SKILL.md",[976,977,978,980,982,984,986,988,990],{"path":415,"priority":340},{"path":422,"priority":418},{"path":979,"priority":418},"references/competitive-alternatives.md",{"path":981,"priority":418},"references/market-category.md",{"path":983,"priority":418},"references/positioning-canvas.md",{"path":985,"priority":418},"references/target-customers.md",{"path":987,"priority":418},"references/team-exercise.md",{"path":989,"priority":418},"references/unique-attributes.md",{"path":991,"priority":418},"references/value-mapping.md",{"basePath":993,"description":994,"displayName":993,"installMethods":995,"rationale":996,"selectedPaths":997,"source":346,"sourceLanguage":18,"type":260},"one-page-marketing","Build a complete marketing plan covering the full customer journey from stranger to raving fan. Use when the user mentions \"marketing plan\", \"target market\", \"USP\", \"lead nurture\", \"customer lifetime value\", \"referral program\", \"marketing strategy\", or \"PVP Index\". Also trigger when building a marketing plan from scratch, choosing acquisition channels, or designing end-to-end customer lifecycle campaigns. Covers the PVP Index, channel selection, and advocacy systems. For brand messaging, see storybrand-messaging. For conversion optimization, see cro-methodology.",{"claudeCode":12},"SKILL.md frontmatter at one-page-marketing/SKILL.md",[998,999,1001,1003,1005,1007,1009,1011,1013,1015,1017],{"path":415,"priority":340},{"path":1000,"priority":418},"references/advertising-media.md",{"path":1002,"priority":418},"references/capture-leads.md",{"path":1004,"priority":418},"references/craft-message.md",{"path":1006,"priority":418},"references/customer-experience.md",{"path":1008,"priority":418},"references/lifetime-value.md",{"path":1010,"priority":418},"references/nurture-leads.md",{"path":1012,"priority":418},"references/one-page-plan-template.md",{"path":1014,"priority":418},"references/referral-systems.md",{"path":1016,"priority":418},"references/sales-conversion.md",{"path":1018,"priority":418},"references/target-market.md",{"basePath":1020,"description":1021,"displayName":1020,"installMethods":1022,"rationale":1023,"selectedPaths":1024,"source":346,"sourceLanguage":18,"type":260},"pragmatic-programmer","Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions \"best practices\", \"pragmatic approach\", \"broken windows\", \"tracer bullet\", \"software craftsmanship\", \"technical debt prevention\", \"prototype vs tracer bullet\", or \"code ownership\". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.",{"claudeCode":12},"SKILL.md frontmatter at pragmatic-programmer/SKILL.md",[1025,1026,1028,1030,1032,1034,1036],{"path":415,"priority":340},{"path":1027,"priority":418},"references/broken-windows.md",{"path":1029,"priority":418},"references/contracts-assertions.md",{"path":1031,"priority":418},"references/dry-orthogonality.md",{"path":1033,"priority":418},"references/estimation-portfolio.md",{"path":1035,"priority":418},"references/reversibility.md",{"path":1037,"priority":418},"references/tracer-bullets.md",{"basePath":1039,"description":1040,"displayName":1039,"installMethods":1041,"rationale":1042,"selectedPaths":1043,"source":346,"sourceLanguage":18,"type":260},"predictable-revenue","Build a scalable outbound B2B sales process with specialized roles (SDR, AE, CSM). Use when the user mentions \"outbound sales\", \"Cold Calling 2.0\", \"prospecting emails\", \"sales pipeline\", \"SDR process\", \"B2B SaaS sales\", \"sales development\", or \"pipeline velocity\". Also trigger when setting up a sales team from scratch, designing cold email sequences, or building qualification frameworks to improve close rates. Covers lead generation, qualification frameworks, and separating prospecting from closing. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.",{"claudeCode":12},"SKILL.md frontmatter at predictable-revenue/SKILL.md",[1044,1045,1046,1048,1050,1051,1053,1055,1057],{"path":415,"priority":340},{"path":422,"priority":418},{"path":1047,"priority":418},"references/cold-calling-2.md",{"path":1049,"priority":418},"references/lead-types.md",{"path":877,"priority":418},{"path":1052,"priority":418},"references/pipeline-math.md",{"path":1054,"priority":418},"references/qualification.md",{"path":1056,"priority":418},"references/roles.md",{"path":1058,"priority":418},"references/team-building.md",{"basePath":1060,"description":1061,"displayName":1060,"installMethods":1062,"rationale":1063,"selectedPaths":1064,"source":346,"sourceLanguage":18,"type":260},"refactoring-patterns","Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions \"refactor this\", \"code smells\", \"extract method\", \"replace conditional\", \"technical debt\", \"move method\", \"inline variable\", or \"decompose conditional\". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.",{"claudeCode":12},"SKILL.md frontmatter at refactoring-patterns/SKILL.md",[1065,1066,1068,1070,1072,1074,1076],{"path":415,"priority":340},{"path":1067,"priority":418},"references/composing-methods.md",{"path":1069,"priority":418},"references/moving-features.md",{"path":1071,"priority":418},"references/organizing-data.md",{"path":1073,"priority":418},"references/refactoring-workflow.md",{"path":1075,"priority":418},"references/simplifying-conditionals.md",{"path":1077,"priority":418},"references/smell-catalog.md",{"basePath":1079,"description":1080,"displayName":1079,"installMethods":1081,"rationale":1082,"selectedPaths":1083,"source":346,"sourceLanguage":18,"type":260},"refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\", \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.",{"claudeCode":12},"SKILL.md frontmatter at refactoring-ui/SKILL.md",[1084,1085,1087,1089,1091,1093],{"path":415,"priority":340},{"path":1086,"priority":418},"references/accessibility-depth.md",{"path":1088,"priority":418},"references/advanced-patterns.md",{"path":1090,"priority":418},"references/animation-microinteractions.md",{"path":1092,"priority":418},"references/data-visualization.md",{"path":1094,"priority":418},"references/theming-dark-mode.md",{"basePath":257,"description":10,"displayName":257,"installMethods":1096,"rationale":1097,"selectedPaths":1098,"source":346,"sourceLanguage":18,"type":260},{"claudeCode":12},"SKILL.md frontmatter at release-it/SKILL.md",[1099,1100,1102,1104,1106,1108,1110],{"path":415,"priority":340},{"path":1101,"priority":418},"references/anti-patterns.md",{"path":1103,"priority":418},"references/capacity-planning.md",{"path":1105,"priority":418},"references/chaos-engineering.md",{"path":1107,"priority":418},"references/deployment-strategies.md",{"path":1109,"priority":418},"references/observability.md",{"path":1111,"priority":418},"references/stability-patterns.md",{"basePath":1113,"description":1114,"displayName":1113,"installMethods":1115,"rationale":1116,"selectedPaths":1117,"source":346,"sourceLanguage":18,"type":260},"scorecard-marketing","Build quiz and assessment funnels that generate qualified leads at 30-50%% conversion. Use when the user mentions \"lead magnet\", \"quiz funnel\", \"assessment tool\", \"lead generation\", \"score-based segmentation\", \"interactive content\", \"lead qualification\", or \"quiz marketing\". Also trigger when designing self-assessment tools, building calculators or graders for marketing, or creating personalized result pages that drive conversions. Covers question design, dynamic results by tier, and automated follow-up sequences. For landing page conversion, see cro-methodology. For full marketing plans, see one-page-marketing.",{"claudeCode":12},"SKILL.md frontmatter at scorecard-marketing/SKILL.md",[1118,1119,1121,1123,1125],{"path":415,"priority":340},{"path":1120,"priority":418},"references/analytics-optimization.md",{"path":1122,"priority":418},"references/industry-examples.md",{"path":1124,"priority":418},"references/psychology.md",{"path":1126,"priority":418},"references/technical-implementation.md",{"basePath":1128,"description":1129,"displayName":1128,"installMethods":1130,"rationale":1131,"selectedPaths":1132,"source":346,"sourceLanguage":18,"type":260},"software-design-philosophy","Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions \"module design\", \"API too complex\", \"shallow class\", \"complexity budget\", \"strategic vs tactical\", \"deep module\", \"information leakage\", or \"pass-through method\". Also trigger when reviewing interface designs for simplicity, evaluating whether an abstraction is pulling its weight, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.",{"claudeCode":12},"SKILL.md frontmatter at software-design-philosophy/SKILL.md",[1133,1134,1136,1138,1140,1142,1144],{"path":415,"priority":340},{"path":1135,"priority":418},"references/comments-as-design.md",{"path":1137,"priority":418},"references/complexity-symptoms.md",{"path":1139,"priority":418},"references/deep-modules.md",{"path":1141,"priority":418},"references/general-vs-special.md",{"path":1143,"priority":418},"references/information-hiding.md",{"path":1145,"priority":418},"references/strategic-programming.md",{"basePath":1147,"description":1148,"displayName":1147,"installMethods":1149,"rationale":1150,"selectedPaths":1151,"source":346,"sourceLanguage":18,"type":260},"storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.",{"claudeCode":12},"SKILL.md frontmatter at storybrand-messaging/SKILL.md",[1152,1153,1155,1157,1159,1161,1163],{"path":415,"priority":340},{"path":1154,"priority":418},"references/brand-script.md",{"path":1156,"priority":418},"references/email-sequences.md",{"path":1158,"priority":418},"references/multi-channel-consistency.md",{"path":1160,"priority":418},"references/one-liners.md",{"path":1162,"priority":418},"references/sales-conversations.md",{"path":1164,"priority":418},"references/website-wireframe.md",{"basePath":227,"description":1166,"displayName":227,"installMethods":1167,"rationale":1168,"selectedPaths":1169,"source":346,"sourceLanguage":18,"type":260},"Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.",{"claudeCode":12},"SKILL.md frontmatter at system-design/SKILL.md",[1170,1171,1172,1174,1176,1178,1180],{"path":415,"priority":340},{"path":656,"priority":418},{"path":1173,"priority":418},"references/common-designs.md",{"path":1175,"priority":418},"references/database-scaling.md",{"path":1177,"priority":418},"references/estimation-numbers.md",{"path":1179,"priority":418},"references/four-step-process.md",{"path":1181,"priority":418},"references/reliability-operations.md",{"basePath":1183,"description":1184,"displayName":1183,"installMethods":1185,"rationale":1186,"selectedPaths":1187,"source":346,"sourceLanguage":18,"type":260},"top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.",{"claudeCode":12},"SKILL.md frontmatter at top-design/SKILL.md",[1188,1189,1191,1192,1194,1196],{"path":415,"priority":340},{"path":1190,"priority":418},"references/animation-patterns.md",{"path":422,"priority":418},{"path":1193,"priority":418},"references/layout-systems.md",{"path":1195,"priority":418},"references/technical-stack.md",{"path":838,"priority":418},{"basePath":1198,"description":1199,"displayName":1198,"installMethods":1200,"rationale":1201,"selectedPaths":1202,"source":346,"sourceLanguage":18,"type":260},"traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V/TO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.",{"claudeCode":12},"SKILL.md frontmatter at traction-eos/SKILL.md",[1203,1204,1205,1207,1208,1210,1212,1214,1216,1218],{"path":415,"priority":340},{"path":422,"priority":418},{"path":1206,"priority":418},"references/data.md",{"path":443,"priority":418},{"path":1209,"priority":418},"references/issues.md",{"path":1211,"priority":418},"references/level-10.md",{"path":1213,"priority":418},"references/people.md",{"path":1215,"priority":418},"references/process.md",{"path":1217,"priority":418},"references/rocks.md",{"path":1219,"priority":418},"references/vto.md",{"basePath":1221,"description":1222,"displayName":1221,"installMethods":1223,"rationale":1224,"selectedPaths":1225,"source":346,"sourceLanguage":18,"type":260},"ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.",{"claudeCode":12},"SKILL.md frontmatter at ux-heuristics/SKILL.md",[1226,1227,1229,1231,1233,1235,1237,1239],{"path":415,"priority":340},{"path":1228,"priority":418},"references/audit-template.md",{"path":1230,"priority":418},"references/cultural-ux.md",{"path":1232,"priority":418},"references/dark-patterns.md",{"path":1234,"priority":418},"references/heuristic-conflicts.md",{"path":1236,"priority":418},"references/krug-principles.md",{"path":1238,"priority":418},"references/nielsen-heuristics.md",{"path":1240,"priority":418},"references/wcag-checklist.md",{"basePath":1242,"description":1243,"displayName":1242,"installMethods":1244,"rationale":1245,"selectedPaths":1246,"source":346,"sourceLanguage":18,"type":260},"web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT/FOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.",{"claudeCode":12},"SKILL.md frontmatter at web-typography/SKILL.md",[1247,1248,1250,1252,1254,1256],{"path":415,"priority":340},{"path":1249,"priority":418},"references/css-implementation.md",{"path":1251,"priority":418},"references/evaluating-typefaces.md",{"path":1253,"priority":418},"references/pairing-strategies.md",{"path":1255,"priority":418},"references/responsive-typography.md",{"path":1257,"priority":418},"references/typeface-anatomy.md",{"sources":1259},[1260],"manual",{"closedIssues90d":8,"description":1262,"forks":247,"homepage":1263,"license":252,"openIssues90d":8,"pushedAt":249,"readmeSize":245,"stars":250,"topics":1264},"Agent skills for Claude Code and other agentskills.io-compatible agents. See https://developertoolkit.ai for more information about skills in general.","https://skills.wondel.ai",[1265,1266,1267,1268,1269,1270,1271,1272,1273,1274],"agent-skills","ai-skills","claude-code","claude-code-marketplace","claude-code-plugin","claude-code-skills","claude-plugins","claude-skills","skill-md","skillsmp",{"classifiedAt":1276,"discoverAt":1277,"extractAt":1278,"githubAt":1278,"updatedAt":1276},1778698867020,1778698861437,1778698864912,[228,230,226,225,229,227],{"evaluatedAt":255,"extractAt":306,"updatedAt":255},[],[1283,1311,1338,1367,1391,1415],{"_creationTime":1284,"_id":1285,"community":1286,"display":1287,"identity":1293,"providers":1297,"relations":1304,"tags":1307,"workflow":1308},1778691344230.1265,"k178zwtykbdxjn221y7gcf952186mynp",{"reviewCount":8},{"description":1288,"installMethods":1289,"name":1291,"sourceUrl":1292},"Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.",{"claudeCode":1290},"jeffallan/claude-skills","Chaos Engineer","https://github.com/jeffallan/claude-skills",{"basePath":1294,"githubOwner":1295,"githubRepo":1272,"locale":18,"slug":1296,"type":260},"skills/chaos-engineer","jeffallan","chaos-engineer",{"evaluate":1298,"extract":1303},{"promptVersionExtension":218,"promptVersionScoring":219,"score":286,"tags":1299,"targetMarket":231,"tier":232},[228,225,312,1300,1301,1302],"devops","testing","failure-injection",{"commitSha":296,"license":252},{"parentExtensionId":1305,"repoId":1306},"k177fx0q0bsftkws6j1av221j186ndt6","kd77w37et655xneae33d1p2d2n86ncxp",[228,1300,312,1302,225,1301],{"evaluatedAt":1309,"extractAt":1310,"updatedAt":1309},1778691495812,1778691344230,{"_creationTime":1312,"_id":1313,"community":1314,"display":1315,"identity":1320,"providers":1323,"relations":1331,"tags":1334,"workflow":1335},1778675056600.2292,"k17263nwckdt8kk4t80p5n3p6x86np5a",{"reviewCount":8},{"description":1316,"installMethods":1317,"name":228,"sourceUrl":1319},"Use when planning, running, or learning from chaos engineering experiments. Triggers on \"chaos experiment\", \"fault injection\", \"gameday\", \"resilience test\", \"blast radius\", \"steady state\", \"abort criteria\", \"Chaos Toolkit\", \"Chaos Mesh\", \"Litmus\", \"Gremlin\", \"AWS FIS\", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + attack taxonomy + tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).",{"claudeCode":1318},"alirezarezvani/claude-skills","https://github.com/alirezarezvani/claude-skills",{"basePath":1321,"githubOwner":1322,"githubRepo":1272,"locale":18,"slug":228,"type":260},"engineering/skills/chaos-engineering","alirezarezvani",{"evaluate":1324,"extract":1330},{"promptVersionExtension":218,"promptVersionScoring":219,"score":286,"tags":1325,"targetMarket":231,"tier":232},[228,225,1326,1327,1328,1329,1301],"fault-injection","sre","reliability","python",{"commitSha":296},{"parentExtensionId":1332,"repoId":1333},"k173223hfbd6c4mx6r1jdx23wn86mbpb","kd7ff9s1w43mfyy1n7hf87816186m6px",[228,1326,1329,1328,225,1327,1301],{"evaluatedAt":1336,"extractAt":1337,"updatedAt":1336},1778678027991,1778675056600,{"_creationTime":1339,"_id":1340,"community":1341,"display":1342,"identity":1348,"providers":1353,"relations":1360,"tags":1363,"workflow":1364},1778695548458.3945,"k17b2gpyw4qf7kn7sakf6jwgex86n7ck",{"reviewCount":8},{"description":1343,"installMethods":1344,"name":1346,"sourceUrl":1347},"Design and execute chaos engineering experiments using Litmus or Chaos Mesh. Test system resilience through controlled fault injection, validate hypothesis-driven tests, and improve failure recovery. Use before major product launches, after architecture changes to validate resilience, during GameDays or disaster recovery drills, to validate assumptions about failure modes, or as part of an SRE maturity program.\n",{"claudeCode":1345},"pjt222/agent-almanac","Run Chaos Experiment","https://github.com/pjt222/agent-almanac",{"basePath":1349,"githubOwner":1350,"githubRepo":1351,"locale":18,"slug":1352,"type":260},"skills/run-chaos-experiment","pjt222","agent-almanac","run-chaos-experiment",{"evaluate":1354,"extract":1359},{"promptVersionExtension":218,"promptVersionScoring":219,"score":222,"tags":1355,"targetMarket":231,"tier":232},[228,1356,225,1326,1357,1358,1327],"kubernetes","litmus","chaos-mesh",{"commitSha":296,"license":252},{"parentExtensionId":1361,"repoId":1362},"k170h0janaa9kwn7cfgfz2ykss86mmh9","kd7aryv63z61j39n2td1aeqkvh86mh12",[228,1358,1326,1356,1357,225,1327],{"evaluatedAt":1365,"extractAt":1366,"updatedAt":1365},1778700975888,1778695548458,{"_creationTime":1368,"_id":1369,"community":1370,"display":1371,"identity":1375,"providers":1377,"relations":1387,"tags":1388,"workflow":1389},1778695548458.3547,"k1797n1eytn5aq9ky9t3f2m23x86n0nf",{"reviewCount":8},{"description":1372,"installMethods":1373,"name":1374,"sourceUrl":1347},"Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.\n",{"claudeCode":1345},"design-on-call-rotation",{"basePath":1376,"githubOwner":1350,"githubRepo":1351,"locale":18,"slug":1374,"type":260},"skills/design-on-call-rotation",{"evaluate":1378,"extract":1386},{"promptVersionExtension":218,"promptVersionScoring":219,"score":1379,"tags":1380,"targetMarket":231,"tier":232},100,[1381,1382,1383,1384,1385,230],"on-call","rotation","escalation","fatigue-management","handoff",{"commitSha":296},{"parentExtensionId":1361,"repoId":1362},[1383,1384,1385,230,1381,1382],{"evaluatedAt":1390,"extractAt":1366,"updatedAt":1390},1778697743701,{"_creationTime":1392,"_id":1393,"community":1394,"display":1395,"identity":1399,"providers":1402,"relations":1411,"tags":1412,"workflow":1413},1778675056600.2373,"k17a55347avnysgdngh6mp591186mfkp",{"reviewCount":8},{"description":1396,"installMethods":1397,"name":1398,"sourceUrl":1319},"Observability Designer (POWERFUL)",{"claudeCode":1318},"Observability Designer",{"basePath":1400,"githubOwner":1322,"githubRepo":1272,"locale":18,"slug":1401,"type":260},"engineering/skills/observability-designer","observability-designer",{"evaluate":1403,"extract":1410},{"promptVersionExtension":218,"promptVersionScoring":219,"score":1379,"tags":1404,"targetMarket":231,"tier":232},[230,1405,1406,1407,1408,1409,1327,1329],"sli","slo","alerting","dashboard","monitoring",{"commitSha":296,"license":252},{"parentExtensionId":1332,"repoId":1333},[1407,1408,1409,230,1329,1405,1406,1327],{"evaluatedAt":1414,"extractAt":1337,"updatedAt":1414},1778678852955,{"_creationTime":1416,"_id":1417,"community":1418,"display":1419,"identity":1423,"providers":1426,"relations":1435,"tags":1436,"workflow":1437},1778695548458.3394,"k172t9vpt2t5qmxmres3sd8chh86nknb",{"reviewCount":8},{"description":1420,"installMethods":1421,"name":1422,"sourceUrl":1347},"Implement circuit breaker logic for agentic tool calls — tracking tool health, transitioning between closed/open/half-open states, reducing task scope when tools fail, routing to alternatives via capability maps, and enforcing failure budgets to prevent error accumulation. Separates orchestration (deciding what to attempt) from execution (calling tools), following the expeditor pattern. Use when building agents that depend on multiple tools with varying reliability, designing fault-tolerant agentic workflows, recovering gracefully from tool outages mid-task, or hardening existing agents against cascading tool failures.\n",{"claudeCode":1345},"Circuit Breaker Pattern",{"basePath":1424,"githubOwner":1350,"githubRepo":1351,"locale":18,"slug":1425,"type":260},"skills/circuit-breaker-pattern","circuit-breaker-pattern",{"evaluate":1427,"extract":1434},{"promptVersionExtension":218,"promptVersionScoring":219,"score":1379,"tags":1428,"targetMarket":231,"tier":232},[225,1429,1430,1431,1432,1433],"circuit-breaker","error-handling","graceful-degradation","tool-reliability","fault-tolerance",{"commitSha":296,"license":252},{"parentExtensionId":1361,"repoId":1362},[1429,1430,1433,1431,225,1432],{"evaluatedAt":1438,"extractAt":1366,"updatedAt":1438},1778696626134]