[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NRNTHD7DK8HJYKFSXY27H3":3,"skill-same:01M6NRNTHD7DK8HJYKFSXY27H3":94},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6NRNTHD7DK8HJYKFSXY27H3","Debugging",null,"Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.","vntopicai\u002Fai-planner","vntopicai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F201040886?v=4","01M6NRHDP3KC0J2F22TSFZH796","01M6NRHDT0JGWD7J4Z10Y0NHHS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"debugging","use","four-phase","fixes","bugs","claims","random","multi","complete","false","call","verification protocols","work","stack","protocols","verification","issues","systematic debugging","test","performance","2026-11-10 10:12:30",false,"---\nname: Debugging\ndescription: Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.\nversion: 3.0.0\nlanguages: all\n---\n\n# Debugging\n\nComprehensive debugging framework combining systematic investigation, root cause tracing, defense-in-depth validation, and verification protocols.\n\n## Core Principle\n\n**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST**\n\nRandom fixes waste time and create new bugs. Find the root cause, fix at source, validate at every layer, verify before claiming success.\n\n## When to Use\n\n**Always use for:** Test failures, bugs, unexpected behavior, performance issues, build failures, integration problems, before claiming work complete\n\n**Especially when:** Under time pressure, \"quick fix\" seems obvious, tried multiple fixes, don't fully understand issue, about to claim success\n\n## The Four Techniques\n\n### 1. Systematic Debugging (`references\u002Fsystematic-debugging.md`)\n\nFour-phase framework ensuring proper investigation:\n- Phase 1: Root Cause Investigation (read errors, reproduce, check changes, gather evidence)\n- Phase 2: Pattern Analysis (find working examples, compare, identify differences)\n- Phase 3: Hypothesis and Testing (form theory, test minimally, verify)\n- Phase 4: Implementation (create test, fix once, verify)\n\n**Key rule:** Complete each phase before proceeding. No fixes without Phase 1.\n\n**Load when:** Any bug\u002Fissue requiring investigation and fix\n\n### 2. Root Cause Tracing (`references\u002Froot-cause-tracing.md`)\n\nTrace bugs backward through call stack to find original trigger.\n\n**Technique:** When error appears deep in execution, trace backward level-by-level until finding source where invalid data originated. Fix at source, not at symptom.\n\n**Includes:** `scripts\u002Ffind-polluter.sh` for bisecting test pollution\n\n**Load when:** Error deep in call stack, unclear where invalid data originated\n\n### 3. Defense-in-Depth (`references\u002Fdefense-in-depth.md`)\n\nValidate at every layer data passes through. Make bugs impossible.\n\n**Four layers:** Entry validation → Business logic → Environment guards → Debug instrumentation\n\n**Load when:** After finding root cause, need to add comprehensive validation\n\n### 4. Verification (`references\u002Fverification.md`)\n\nRun verification commands and confirm output before claiming success.\n\n**Iron law:** NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE\n\nRun the command. Read the output. Then claim the result.\n\n**Load when:** About to claim work complete, fixed, or passing\n\n## Quick Reference\n\n```\nBug → systematic-debugging.md (Phase 1-4)\n  Error deep in stack? → root-cause-tracing.md (trace backward)\n  Found root cause? → defense-in-depth.md (add layers)\n  About to claim success? → verification.md (verify first)\n```\n\n## Red Flags\n\nStop and follow process if thinking:\n- \"Quick fix for now, investigate later\"\n- \"Just try changing X and see if it works\"\n- \"It's probably X, let me fix that\"\n- \"Should work now\" \u002F \"Seems fixed\"\n- \"Tests pass, we're done\"\n\n**All mean:** Return to systematic process.\n","# Debugging\n\nComprehensive debugging framework combining systematic investigation, root cause tracing, defense-in-depth validation, and verification protocols.\n\n## Core Principle\n\n**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST**\n\nRandom fixes waste time and create new bugs. Find the root cause, fix at source, validate at every layer, verify before claiming success.\n\n## When to Use\n\n**Always use for:** Test failures, bugs, unexpected behavior, performance issues, build failures, integration problems, before claiming work complete\n\n**Especially when:** Under time pressure, \"quick fix\" seems obvious, tried multiple fixes, don't fully understand issue, about to claim success\n\n## The Four Techniques\n\n### 1. Systematic Debugging (`references\u002Fsystematic-debugging.md`)\n\nFour-phase framework ensuring proper investigation:\n- Phase 1: Root Cause Investigation (read errors, reproduce, check changes, gather evidence)\n- Phase 2: Pattern Analysis (find working examples, compare, identify differences)\n- Phase 3: Hypothesis and Testing (form theory, test minimally, verify)\n- Phase 4: Implementation (create test, fix once, verify)\n\n**Key rule:** Complete each phase before proceeding. No fixes without Phase 1.\n\n**Load when:** Any bug\u002Fissue requiring investigation and fix\n\n### 2. Root Cause Tracing (`references\u002Froot-cause-tracing.md`)\n\nTrace bugs backward through call stack to find original trigger.\n\n**Technique:** When error appears deep in execution, trace backward level-by-level until finding source where invalid data originated. Fix at source, not at symptom.\n\n**Includes:** `scripts\u002Ffind-polluter.sh` for bisecting test pollution\n\n**Load when:** Error deep in call stack, unclear where invalid data originated\n\n### 3. Defense-in-Depth (`references\u002Fdefense-in-depth.md`)\n\nValidate at every layer data passes through. Make bugs impossible.\n\n**Four layers:** Entry validation → Business logic → Environment guards → Debug instrumentation\n\n**Load when:** After finding root cause, need to add comprehensive validation\n\n### 4. Verification (`references\u002Fverification.md`)\n\nRun verification commands and confirm output before claiming success.\n\n**Iron law:** NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE\n\nRun the command. Read the output. Then claim the result.\n\n**Load when:** About to claim work complete, fixed, or passing\n\n## Quick Reference\n\n```\nBug → systematic-debugging.md (Phase 1-4)\n  Error deep in stack? → root-cause-tracing.md (trace backward)\n  Found root cause? → defense-in-depth.md (add layers)\n  About to claim success? → verification.md (verify first)\n```\n\n## Red Flags\n\nStop and follow process if thinking:\n- \"Quick fix for now, investigate later\"\n- \"Just try changing X and see if it works\"\n- \"It's probably X, let me fix that\"\n- \"Should work now\" \u002F \"Seems fixed\"\n- \"Tests pass, we're done\"\n\n**All mean:** Return to systematic process.\n",{"name":5,"version":43,"languages":44,"description":7},"3.0.0","all","main","c6237323cdebe9c0193c97f1a338cb169728d78d","fixtures\u002Flocal-skills\u002Fdebugging",0,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner","https:\u002F\u002Fgithub.com\u002Fvntopicai","2026-05-13 18:29:40",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vntopicai\u002Fai-planner --skill Debugging",{"tool":58,"command":59},"bunx","bunx skills add vntopicai\u002Fai-planner --skill Debugging",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vntopicai\u002Fai-planner --skill Debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002FSKILL.md",true,[66,72,76,80,84,90],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fdefense-in-depth.md","REFERENCE","参考文档",3662,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Freferences\u002Fdefense-in-depth.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Froot-cause-tracing.md",3356,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Freferences\u002Froot-cause-tracing.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsystematic-debugging.md",4158,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Freferences\u002Fsystematic-debugging.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fverification.md",3399,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Freferences\u002Fverification.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Ffind-polluter.sh","SCRIPT","脚本",1520,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Fscripts\u002Ffind-polluter.sh",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Ffind-polluter.test.md",2117,"https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fdebugging\u002Fscripts\u002Ffind-polluter.test.md",[95,138,150,166,193,220],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":117,"publishedAt":38},"01M6NRX0GTVS1XTC035TQFBD6R","ui-ux-pro-max","Frontend UI\u002FUX design intelligence - activate FIRST when user requests beautiful, stunning, gorgeous, or aesthetic interfaces. The primary skill for design decisions before implementation. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check frontend UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fui-ux-pro-max\u002FSKILL.md",[101,106,109,112],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":110,"categoryName":111,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"ui ux","ux","ui","ui ux pro max","max","pro","Tailwind","mode","card","chart","app","tsx","fix","projects","improve","Charts","Animation","actions","design","frontend",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":38},"01M6NRWHBP9GJK3QP0SDZ5JKMZ","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Ftemplate-skill\u002FSKILL.md",[144],{"categoryNo":110,"categoryName":111,"taxonomyType":104,"taxonomyTypeDesc":105},[146,147,148,149,19],"template skill","template","with","it",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":38},"01M6NRW447KC6JHJETVDTS0D25","research","Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fresearch\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000021","资料检索与研究",[152,160,161,162,163,19,164,165],"secure","plan","analyze","technical","Scalable","you",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":38},"01M6NRVG7DA75KBK2XKCHQW8YT","Problem-Solving Techniques","Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fproblem-solving\u002FSKILL.md",[],[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192],"techniques","Problem Solving Techniques","problem","problem solving","uncertainty","simplification","apply","inversion","for","Inversion Exercise","project","problem-solving","thinking","Scale Game","complexity","recurring","game","exercise","Meta","when stuck",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":38},"01M6NRV95P9DA08M92S4BHRG1M","payment-integration","Implement payment integrations with SePay (Vietnamese payment gateway with VietQR, bank transfers, cards) and Polar (global SaaS monetization platform with subscriptions, usage-based billing, automated benefits). Use when integrating payment processing, implementing checkout flows, managing subscriptions, handling webhooks, processing bank transfers, generating QR codes, automating benefit delivery, or building billing systems. Supports authentication (API keys, OAuth2), product management, customer portals, tax compliance (Polar as MoR), and comprehensive SDK integrations (Node.js, PHP, Python, Go, Laravel, Next.js).","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fpayment-integration\u002FSKILL.md",[],[200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219],"payment","payment integration","integration","laravel","api","product","authentication","customer","node","implementing","api keys","bank","transfers","qr","flows","billing","processing","checkout","delivery","next",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":38},"01M6NRV5BXB7JXQXWBHQJZ36AJ","nodejs-best-practices","Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.","https:\u002F\u002Fgithub.com\u002Fvntopicai\u002Fai-planner\u002Fblob\u002Fmain\u002Ffixtures\u002Flocal-skills\u002Fnodejs-best-practices\u002FSKILL.md",[],[227,228,229,230,231,232,233,234,185,235,236,237,208,238,239,240,241,242,243],"best practices","nodejs","nodejs best practices","selection","unknown","principles","decision-making","patterns","community","async","framework selection","decision","js","framework","development","architecture","security"]