Systematic debugging methodologies for hard bugs. Covers rubber ducking, code tracing, hypothesis testing, logging strategies. Use when stuck on bugs that resist quick fixes.
Applies systematic debugging methods to diagnose and resolve complex software bugs.
npx claudepluginhub captaincrouton89/crouton-kitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
frontend.mdQuote code snippets and explain what each chunk should do vs actually does. Don't assume—verbalize the logic. Discrepancies reveal bugs.
Trace data from entry point to failure. At each transformation: what goes in, what comes out? Mark where expectations diverge.
Failure-prone boundaries: async, serialization, type coercion, null propagation, state mutations.
Don't change code hoping it helps—that creates noise.
Log at decision points and async boundaries, not everywhere.
Workflow:
For complex/unfamiliar code sections acting as a blackbox:
When stuck: Spawn 2-3 senior-advisor agents in parallel with different perspectives (pragmatist, architect, skeptic).
Avoid biasing agents: Pass them relevant file paths and the observed behavior, but not your hypotheses or assumptions. Let them form independent conclusions.
If no, keep investigating.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.