๐Ÿ›Debugging Skills

Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.

989 skills ยท Page 11 of 42

axiom-swiftui-debugging

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when debugging SwiftUI view updates, preview crashes, or layout issues - diagnostic decision trees to identify root causes quickly and avoid misdiagnosis under pressure

axiom-metal-migration-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when ANY Metal porting issue occurs - black screen, rendering artifacts, shader errors, wrong colors, performance regressions, GPU crashes

axiom-foundation-models-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when debugging Foundation Models issues โ€” context exceeded, guardrail violations, slow generation, availability problems, unsupported language, or unexpected output. Systematic diagnostics with production crisis defense.

axiom-camera-capture-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

camera freezes, preview rotated wrong, capture slow, session interrupted, black preview, front camera mirrored, camera not starting, AVCaptureSession errors, startRunning blocks, phone call interrupts camera

axiom-background-processing

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when implementing BGTaskScheduler, debugging background tasks that never run, understanding why tasks terminate early, or testing background execution - systematic task lifecycle management with proper registration, expiration handling, and Swift 6 cancellation patterns

axiom-swiftui-debugging-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when SwiftUI view debugging requires systematic investigation - view updates not working after basic troubleshooting, intermittent UI issues, complex state dependencies, or when Self._printChanges() shows unexpected update patterns - systematic diagnostic workflows with Instruments integration

axiom-swiftdata-migration-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when SwiftData migrations crash, fail to preserve relationships, lose data, or work in simulator but fail on device - systematic diagnostics for schema version mismatches, relationship errors, and migration testing gaps

axiom-core-location-diag

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use for Core Location troubleshooting - no location updates, background location broken, authorization denied, geofence not triggering

axiom-xcode-debugging

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when encountering BUILD FAILED, test crashes, simulator hangs, stale builds, zombie xcodebuild processes, "Unable to boot simulator", "No such module" after SPM changes, or mysterious test failures despite no code changes - systematic environment-first diagnostics for iOS/macOS projects

axiom-swiftui-performance

CharlesWiltgen's avatarfrom CharlesWiltgenโ˜… 181

Use when UI is slow, scrolling lags, animations stutter, or when asking 'why is my SwiftUI view slow', 'how do I optimize List performance', 'my app drops frames', 'view body is called too often', 'List is laggy' - SwiftUI performance optimization with Instruments 26 and WWDC 2025 patterns

debug

Thank-you-Linus's avatarfrom Thank-you-Linusโ˜… 113

Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration. Use when investigating errors, analyzing stack traces, fixing bugs, or troubleshooting unexpected behavior.

debug-helper

einverne's avatarfrom einverneโ˜… 109

Systematic debugging strategies, troubleshooting methodologies, and problem-solving techniques for code and system issues. Use when the user encounters bugs, errors, or unexpected behavior and needs help diagnosing and resolving problems.

debug-logging-assistant

dmitriiweb's avatarfrom dmitriiwebโ˜… 106

Add purposeful debug logging to improve observability without changing behavior.

observability-first-debugging

NTCoding's avatarfrom NTCodingโ˜… 93

Systematic debugging methodology that eliminates guessing and speculation. Add instrumentation to gather specific data that fully explains the problem. Evidence before hypothesis. Observation before solution.

troubleshoot

Chachamaru127's avatarfrom Chachamaru127โ˜… 85

Guides diagnosis and resolution when problems occur. Use when user mentions ๅ‹•ใ‹ใชใ„, ใ‚จใƒฉใƒผใŒๅ‡บใŸ, ๅฃŠใ‚ŒใŸ, ใ†ใพใใ„ใ‹ใชใ„, broken, doesn't work, error. Do NOT load for: ๆญฃๅธธใชใƒ“ใƒซใƒ‰, ๆ–ฐๆฉŸ่ƒฝๅฎŸ่ฃ…, ใƒฌใƒ“ใƒฅใƒผ.

python-performance

athola's avatarfrom atholaโ˜… 83

Profile and optimize Python code using cProfile, memory profilers, andperformance best practices.Triggers: profiling, optimization, cProfile, memory profiler, bottleneck,slow code, performance, benchmarking, py-spy, tracemallocUse when: debugging slow code, identifying bottlenecks, optimizing memory,benchmarking performance, production profilingDO NOT use when: async concurrency - use python-async instead.DO NOT use when: CPU/GPU system monitoring - use conservation:cpu-gpu-performance.Consult this skill for Python performance profiling and optimization.

symbolication-setup

nexus-labs-automation's avatarfrom nexus-labs-automationโ˜… 70

Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).

performing-systematic-debugging-for-stubborn-problems

sammcj's avatarfrom sammcjโ˜… 65

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.

systematic-debugging

xenitV1's avatarfrom xenitV1โ˜… 62

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

root-cause-tracing

korallis's avatarfrom korallisโ˜… 49

Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.

debugging-systematic

korallis's avatarfrom korallisโ˜… 49

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

deep-research

glittercowboy's avatarfrom glittercowboyโ˜… 47

Multi-agent parallel investigation for complex JUCE problems. Use when troubleshooting fails after Level 3, problems require novel research, or user requests /research command.

c-memory-management

TheBushidoCollective's avatarfrom TheBushidoCollectiveโ˜… 47

Use when managing memory in C programs with malloc/free, pointers, and avoiding common memory safety pitfalls.

performance-optimization

TheBushidoCollective's avatarfrom TheBushidoCollectiveโ˜… 47

Use when optimizing code for performance, reducing bundle size, improving load times, or fixing performance bottlenecks. Emphasizes measurement-driven optimization.

โ† Back to All Skills