[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79Z5N8QZ3FGEMC3VESTEENV":3,"skill-same:01M79Z5N8QZ3FGEMC3VESTEENV":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M79Z5N8QZ3FGEMC3VESTEENV","debug-mantra",null,"Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on \u002Fdebug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken\u002Fthrowing\u002Ffailing, asks to debug\u002Fdiagnose\u002Finvestigate an issue, or pastes a stack trace or error log.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdebug-mantra\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: debug-mantra\ndescription: \"Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on \u002Fdebug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken\u002Fthrowing\u002Ffailing, asks to debug\u002Fdiagnose\u002Finvestigate an issue, or pastes a stack trace or error log.\"\nuser-invocable: true\n---\n\n# Debug Mantra\n\nFour-step discipline for any debug session. Recite verbatim, then apply in order.\n\n## Recite this — verbatim, as the first thing in your first response\n\n> **Mantra:**\n>\n> 1. **First is reproducibility.** Can the issue be reproduced reliably?\n> 2. **Know the fail path.** Debugger first; then source trace + knob enumeration; then in-code instrumentation.\n> 3. **Question your hypothesis.** What would disprove it?\n> 4. **Every run is a breadcrumb.** Cross-reference all of them.\n\nThen begin work.\n\n---\n\n## 1. Reproduce reliably\n\nBuild a runnable repro before anything else.\n\n- **Reliable repro** → capture the exact steps, inputs, and environment as a runnable artifact: failing test, curl script, CLI invocation, replay harness.\n- **Flaky repro** → the bug is not yet debuggable. Raise the rate first: loop the trigger, parallelise, add stress, narrow timing windows, inject sleeps. 50% flake is debuggable; 1% is not.\n- **No repro at all** → stop. Say so explicitly. Ask the user for env access, captured artifacts (HAR, log dump, core), or permission to instrument. Do **not** proceed to hypothesise.\n\nTarget: a fast (1–5 s), deterministic pass\u002Ffail signal. Pin time, seed the RNG, freeze network, isolate filesystem.\n\n---\n\n## 2. Know the fail path\n\nOnce reproducible, find _where_ the code breaks and _what stops it from breaking_. The differential narrows the search. Try in this order — escalate only when the prior tactic fails.\n\n1. **Attach a debugger.** If the env supports it, attach and step to the failure site. One breakpoint beats ten logs. Do this **before** turning any knobs.\n2. **Source trace + knob enumeration.** If no debugger (or it can't reach the bug), trace the code path end-to-end and list every knob that can influence the outcome:\n   - config flags, env vars, feature toggles\n   - branch conditions, input shape\n   - timing, concurrency, build options\n     Each knob is a candidate axis to flip in the differential. Flip one at a time.\n3. **In-code instrumentation.** If outside knobs can't move the failure, go inside: `printf` \u002F log statements at the suspected fail site, dump the relevant internal state. Tag every probe with a unique prefix (e.g. `[DBG-a4f2]`) so cleanup is a single grep. Let the trace show where reality diverges from your model.\n\n---\n\n## 3. Falsify the hypothesis\n\nWhen a candidate root cause surfaces, scrutinise it **before** testing it.\n\n- Does it actually explain the symptom end-to-end? Walk it through.\n- What is the simplest **proof**? What is the cleanest **disproof**?\n- Run the **disproof first**. If the hypothesis survives, it's real. If it dies, you saved yourself from chasing a phantom.\n- Generate 3–5 ranked hypotheses, not one. Single-hypothesis thinking anchors on the first plausible idea.\n\n---\n\n## 4. Every run is a breadcrumb\n\nMaintain a running **ledger** of every experiment in this session. Each entry: what changed, what happened, what it ruled in or out.\n\n- When a new hypothesis surfaces, walk the ledger. Does it hold for **every** prior observation, not just the most recent?\n- If any past run contradicts it, the hypothesis is wrong or incomplete — refine or discard.\n- When in doubt, design the **single experiment** whose outcome makes it certain. Run that next, instead of churning on adjacent runs.\n- Update the ledger after every run. It is your memory across the session.\n\n---\n\n## Operating rules\n\n- Recite the mantra block **once** per debug session, in your first response. Do not re-recite mid-session.\n- Recite **verbatim**. Never paraphrase, shorten, or skip lines of the recital.\n- If the user says \"skip the mantra\" → skip the recital but still apply the four steps silently.\n- Apply the four steps **in order**:\n  - Do not propose a fix before #1 is satisfied (reliable repro exists).\n  - Do not start testing hypotheses before #2 has narrowed the fail path.\n  - Do not commit to a hypothesis before #3 has tried to disprove it.\n  - Do not declare a hypothesis correct until #4 confirms it against every prior breadcrumb.\n- If you catch yourself proposing a fix without a reliable repro, stop and return to step 1.\n- The mantra is a constraint **you** carry through the session — not advice to deliver back to the user.\n","# Debug Mantra\n\nFour-step discipline for any debug session. Recite verbatim, then apply in order.\n\n## Recite this — verbatim, as the first thing in your first response\n\n> **Mantra:**\n>\n> 1. **First is reproducibility.** Can the issue be reproduced reliably?\n> 2. **Know the fail path.** Debugger first; then source trace + knob enumeration; then in-code instrumentation.\n> 3. **Question your hypothesis.** What would disprove it?\n> 4. **Every run is a breadcrumb.** Cross-reference all of them.\n\nThen begin work.\n\n---\n\n## 1. Reproduce reliably\n\nBuild a runnable repro before anything else.\n\n- **Reliable repro** → capture the exact steps, inputs, and environment as a runnable artifact: failing test, curl script, CLI invocation, replay harness.\n- **Flaky repro** → the bug is not yet debuggable. Raise the rate first: loop the trigger, parallelise, add stress, narrow timing windows, inject sleeps. 50% flake is debuggable; 1% is not.\n- **No repro at all** → stop. Say so explicitly. Ask the user for env access, captured artifacts (HAR, log dump, core), or permission to instrument. Do **not** proceed to hypothesise.\n\nTarget: a fast (1–5 s), deterministic pass\u002Ffail signal. Pin time, seed the RNG, freeze network, isolate filesystem.\n\n---\n\n## 2. Know the fail path\n\nOnce reproducible, find _where_ the code breaks and _what stops it from breaking_. The differential narrows the search. Try in this order — escalate only when the prior tactic fails.\n\n1. **Attach a debugger.** If the env supports it, attach and step to the failure site. One breakpoint beats ten logs. Do this **before** turning any knobs.\n2. **Source trace + knob enumeration.** If no debugger (or it can't reach the bug), trace the code path end-to-end and list every knob that can influence the outcome:\n   - config flags, env vars, feature toggles\n   - branch conditions, input shape\n   - timing, concurrency, build options\n     Each knob is a candidate axis to flip in the differential. Flip one at a time.\n3. **In-code instrumentation.** If outside knobs can't move the failure, go inside: `printf` \u002F log statements at the suspected fail site, dump the relevant internal state. Tag every probe with a unique prefix (e.g. `[DBG-a4f2]`) so cleanup is a single grep. Let the trace show where reality diverges from your model.\n\n---\n\n## 3. Falsify the hypothesis\n\nWhen a candidate root cause surfaces, scrutinise it **before** testing it.\n\n- Does it actually explain the symptom end-to-end? Walk it through.\n- What is the simplest **proof**? What is the cleanest **disproof**?\n- Run the **disproof first**. If the hypothesis survives, it's real. If it dies, you saved yourself from chasing a phantom.\n- Generate 3–5 ranked hypotheses, not one. Single-hypothesis thinking anchors on the first plausible idea.\n\n---\n\n## 4. Every run is a breadcrumb\n\nMaintain a running **ledger** of every experiment in this session. Each entry: what changed, what happened, what it ruled in or out.\n\n- When a new hypothesis surfaces, walk the ledger. Does it hold for **every** prior observation, not just the most recent?\n- If any past run contradicts it, the hypothesis is wrong or incomplete — refine or discard.\n- When in doubt, design the **single experiment** whose outcome makes it certain. Run that next, instead of churning on adjacent runs.\n- Update the ledger after every run. It is your memory across the session.\n\n---\n\n## Operating rules\n\n- Recite the mantra block **once** per debug session, in your first response. Do not re-recite mid-session.\n- Recite **verbatim**. Never paraphrase, shorten, or skip lines of the recital.\n- If the user says \"skip the mantra\" → skip the recital but still apply the four steps silently.\n- Apply the four steps **in order**:\n  - Do not propose a fix before #1 is satisfied (reliable repro exists).\n  - Do not start testing hypotheses before #2 has narrowed the fail path.\n  - Do not commit to a hypothesis before #3 has tried to disprove it.\n  - Do not declare a hypothesis correct until #4 confirms it against every prior breadcrumb.\n- If you catch yourself proposing a fix without a reliable repro, stop and return to step 1.\n- The mantra is a constraint **you** carry through the session — not advice to deliver back to the user.\n",{"name":5,"description":7,"user-invocable":24},true,"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fdebug-mantra","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add kongnakornna\u002Fgolangapi --skill debug-mantra",{"tool":39,"command":40},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill debug-mantra",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill debug-mantra","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdebug-mantra\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"SKILLTH.md","REFERENCE","参考文档",13506,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdebug-mantra\u002FSKILLTH.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]