メニュー
Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
Meta-orchestrator for debugging and fixing. Analyzes bugs/errors and auto-selects the best combination of skills from .agents/skills/ to diagnose and resolve. Use when encountering bugs, errors, test failures, performance issues, broken UI, or any code that isn't working as expected.
Meta-orchestrator for feature implementation. Analyzes feature requests and auto-selects the best combination of skills from .agents/skills/ to execute. Use when building new features, adding functionality, creating UI components, implementing APIs, or any constructive development task.
Build 3D web apps with Three.js (WebGL/WebGPU). Use for 3D scenes, animations, custom shaders, PBR materials, VR/XR experiences, games, data visualizations, product configurators.
| name | debugging |
| description | Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols |
| when_to_use | when encountering bugs, test failures, unexpected behavior, or needing to validate fixes before claiming completion |
| version | 1.0.0 |
| languages | all |
A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.
Location: systematic-debugging/SKILL.md
Four-phase debugging framework: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation. The iron law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Location: root-cause-tracing/SKILL.md
Trace bugs backward through the call stack to find the original trigger. Don't fix symptoms - find where invalid data originated and fix at the source.
Location: defense-in-depth/SKILL.md
Validate at every layer data passes through to make bugs structurally impossible. Four layers: Entry Point → Business Logic → Environment Guards → Debug Instrumentation.
Location: verification-before-completion/SKILL.md
Run verification commands and confirm output before claiming success. The iron law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
| Symptom | Sub-Skill |
|---|---|
| Test failure, unexpected behavior | systematic-debugging |
| Error appears in wrong location | root-cause-tracing |
| Same bug keeps recurring | defense-in-depth |
| Need to confirm fix works | verification-before-completion |
"Systematic debugging is FASTER than guess-and-check thrashing."
From real debugging sessions:
