Loading...
Loading...
Found 1,682 Skills
Diagnose SwiftUI performance issues including unnecessary re-renders, view identity problems, and slow body evaluations. Use when SwiftUI views are slow, janky, or re-rendering too often.
Debug network issues using browser tools and network analysis. Diagnose connection problems, latency, and data transmission issues.
Debug database performance issues through query analysis, index optimization, and execution plan review. Identify and fix slow queries.
Use when CAAnimation completion handler doesn't fire, spring physics look wrong on device, animation duration mismatches actual time, gesture + animation interaction causes jank, or timing differs between simulator and real hardware - systematic CAAnimation diagnosis with CATransaction patterns, frame rate awareness, and device-specific behavior
Debug and diagnose model errors in Pollinations services. Analyze logs, find error patterns, identify affected users. For taking action on user tiers, see tier-management skill.
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.
iOS debugging and troubleshooting skills. Used when users need to investigate and diagnose issues such as crashes, exceptions, runtime errors, memory leaks, memory growth, unreleased ViewController, UI lag, frame drops, slow startup, etc. Provides crash type identification, root cause analysis, LLDB commands and repair solutions.
Trace bugs through call chains using knowledge graph
Question-only debugging mode that guides users to find root causes themselves through structured questioning. Never gives answers directly. Escalates to systematic-debugging after 12 questions if no progress. Use when: "rubber duck", "help me think through this bug", "debug with me", "walk me through debugging", "socratic debug", "think through this issue"
Evidence-based 4-phase root cause analysis: Reproduce, Isolate, Identify, Verify. Use when user reports a bug, tests are failing, code introduced regressions, or production issues need investigation. Use for "debug", "fix bug", "why is this failing", "root cause", or "tests broken". Do NOT use for feature requests, refactoring, or performance optimization without a specific bug symptom.
Debug React applications by inspecting components, props, and the component tree. Use when the user is debugging React apps, wants to inspect component props/state, find which component renders an element, or understand the React component hierarchy.
Mobile app debugging for iOS, Android, cross-platform frameworks. Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments, Android Profiler, React Native debugger, native bridge errors.