Loading...
Loading...
Found 1,626 Skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Systematically debug code issues using proven methodologies. Use when encountering errors, unexpected behavior, or performance problems. Handles error analysis, root cause identification, debugging strategies, and fix verification.
Activate this skill when any task fails two or more times, when you are about to give up or say 'I cannot', when shifting responsibility to the user (e.g., 'you should manually...', 'please check...', 'you may need to...'), blaming the environment without verification (e.g., 'might be a permissions issue', 'could be a network problem'), making any excuse to stop trying, spinning in circles (repeatedly tweaking the same code/parameters without new information — busywork), fixing only the surface issue without checking for related problems, skipping verification after a fix and claiming 'done', providing suggestions instead of actual code/commands, saying 'this is beyond scope' or 'this requires manual intervention', encountering permission/network/auth errors and stopping instead of trying alternatives, or displaying any passive behavior (waiting for user instructions instead of proactively investigating). It also triggers on user frustration phrases in any language: '你怎么又失败了', '为什么还不行', '换个方法', '你再试试', '不要放弃', '继续', '加油', 'why does this still not work', 'try harder', 'you keep failing', 'stop giving up', 'try again', 'don't give up', 'keep going', 'figure it out'. This applies to ALL task types: debugging, implementation, configuration, deployment, research, DevOps, infrastructure, API integration, data processing. Do NOT activate it for first-attempt failures or when a known fix is already in progress.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Use when encountering "Unable to simultaneously satisfy constraints" errors, constraint conflicts, ambiguous layout warnings, or views positioned incorrectly - systematic debugging workflow for Auto Layout issues in iOS
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
Debug issues that occur sporadically and are hard to reproduce. Use monitoring and systematic investigation to identify root causes of flaky behavior.
Systematic debugging playbook for application errors and incidents: crashes, regressions, intermittent failures, production-only bugs, performance issues, stack traces, log/trace analysis, profiling, and distributed systems root cause analysis.
Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
Monitor and debug Eve jobs with CLI follow, logs, wait, and diagnose commands. Use when work is stuck, failing, or you need fast status.