systematic-debugging

Description

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Tool Access

Full access

Inherits all available tools

Supporting Files

5 files

Additional assets for this skill

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

CREATION-LOG.md

test-academic.md

test-pressure-1.md

test-pressure-2.md

test-pressure-3.md

Links

GitHub Stats

0 forks

Updated 25 days ago

Related Skills

Writing Hookify Rules

46.0K

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

From hookify

frontend-design

46.0K

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

From frontend-design

claude-opus-4-5-migration

46.0K

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

From claude-opus-4-5-migration