Loading...
Loading...
Found 27 Skills
Use when encountering errors, bugs, unexpected behavior, or any problem requiring systematic debugging with extended thinking for complex multi-layer issues
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
Use this whenever you encounter any bugs, test failures, or abnormal behavior, and execute it before proposing a fix
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.
Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming hypotheses and validating them with specific tasks.
Root-cause discipline for bugs, test failures, and unexpected behavior. Embedded grill on the hypothesis before writing fix code. Use when encountering any bug, failing test, or behavior that doesn't match expectation.
Iterative debug loop for Luau/Roblox issues
4-phase root cause debugging: understand bugs before fixing.
Root-cause investigation for bugs, regressions, suspicious runtime behavior, failed automations, and unexpected outcomes.
State-machine driven orchestrator for structured software development. Invoke when user wants to develop features, fix bugs, or refactor code. Triggers: 'build a feature', 'fix this bug', 'implement', 'develop', 'refactor'.
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
Helps fail fast on risky implementation steps by prototyping before committing to full code changes. Use during planning or implementation when a step is ambiguous, depends on multiple subsystems or flaky tools, may invalidate the current plan, or when repeated fix attempts suggest a doom loop. Useful both at planning step and during implementation.