菜单
Find the root cause before changing code. Use when encountering any bug, test failure, crash, flaky test, performance regression, or unexpected behavior, before proposing or applying a fix.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | systematic-debugging |
| description | Find the root cause before changing code. Use when encountering any bug, test failure, crash, flaky test, performance regression, or unexpected behavior, before proposing or applying a fix. |
Guessing creates new bugs and hides old ones. Find the root cause first.
No fix without a root-cause hypothesis you have confirmed with evidence.
If you cannot explain why the bug happens, you are not ready to fix it.
Any test failure, crash, wrong output, flaky test, performance regression, build failure, or integration issue — especially when under time pressure or when a previous fix didn't hold.
git bisect, binary search by
commenting/disabling, or diffing a working vs broken state.git bisect to locate the introducing commit.-race / repeated runs.if x == nil guards without knowing why x is nil.Optimize React/Next.js runtime performance — eliminate waterfalls, shrink bundles, cut unnecessary re-renders, and speed up rendering. Use when writing, reviewing, or refactoring components for speed, or chasing slow renders, large bundles, janky interactions, or high TTFB/LCP/INP.
Build agent-friendly web apps with the W3C Web Model Context API (WebMCP). Use when exposing frontend features as structured tools for in-browser AI agents, adding document.modelContext tools to React/Next.js apps, designing tool schemas for dashboards or admin UIs, or making existing UI automatable without DOM scraping.
Write clear, fast, deterministic Go tests including mandatory repo integration tests (x/testkit) and app unit tests. Use when adding or fixing Go tests, implementing internal/repo or internal/app, designing table-driven tests, writing benchmarks, using testify, or improving coverage in this workspace.
Design distinctive, production-grade frontend interfaces that don't read as templated AI defaults. Use when bootstrapping a frontend app, building or restyling a landing page, marketing site, hero, brand-forward product surface, or any UI where visual identity matters — choosing palette, typography, layout, motion, and copy. Required before running create-next-app or writing UI.
Review code (your own or others') for correctness, design, and risk before it merges. Use when reviewing a diff or pull request, doing a self-review before opening a PR, or giving structured, prioritized feedback.
Architect a scalable, themeable design-token system — primitive → semantic → component layers, CSS variables, a 4px spacing/type scale, and dark mode. Use when setting up or refactoring a project's tokens, naming color/spacing/radius values, wiring tokens into Tailwind/shadcn, enabling theme switching, or killing hard-coded hex/px scattered through components.