Debugging
Find and fix bugs, error analysis
agent-introspection-debugging
by affaan-m
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
click-path-audit
by affaan-m
"Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores."
security-review
by affaan-m
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
golang-concurrency-patterns
by bobmatnyc
"Go concurrency patterns for production services: context cancellation, errgroup, worker pools, bounded parallelism, fan-in/fan-out, and common race/deadlock pitfalls"
godot-genre-sports
by thedivergentai
"Expert blueprint for sports games (FIFA, NBA 2K, Rocket League, Tony Hawk) covering physics-based ball interaction, team AI formations, contextual input, and broadcast camera systems. Use when building soccer, basketball, hockey, racing sports, or arcade sports games. Keywords ball physics, magnus effect, formation AI, team tactics, contextual controls, steering behaviors."
godot-genre-open-world
by thedivergentai
"Expert blueprint for open world games including chunk-based streaming (load/unload regions dynamically), floating origin (prevent precision jitter beyond 5000 units), HLOD (hierarchical LOD for distant meshes), persistent state (track entity changes across unloaded chunks), POI discovery systems (compass, markers), and threaded loading (prevent stutters). Use for RPGs, sandboxes, or exploration games. Trigger keywords: open_world, chunk_streaming, floating_origin, HLOD, persistent_state, POI_discovery, threaded_loading."
senior-mobile
by borghei
Expert mobile development covering iOS, Android, React Native, and Flutter for native and cross-platform applications.
senior-mobile
by borghei
Expert mobile development covering iOS, Android, React Native, and Flutter for native and cross-platform applications.
delivery-manager
by borghei
Expert delivery management covering continuous delivery, release management, deployment coordination, and service operations.
receiving-code-review
by obra
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
refactoring
by citypaul
Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities.
godot-genre-battle-royale
by thedivergentai
"Expert blueprint for Battle Royale games including shrinking zone/storm mechanics (phase-based, damage scaling), large-scale networking (relevancy, tick rate optimization), deployment systems (plane, freefall, parachute), loot spawning (weighted tables, rarity), and performance optimization (LOD, occlusion culling, object pooling). Use for multiplayer survival games or last-one-standing formats. Trigger keywords: battle_royale, zone_shrink, storm_damage, deployment_system, loot_spawn, networking_optimization, relevancy_system, snapshot_interpolation."
test-driven-development
by obra
Use when implementing any feature or bugfix, before writing implementation code
generate-component-story
by longbridge
Create story examples for components. Use when writing stories, creating examples, or demonstrating component usage.
functional
by citypaul
Functional programming patterns with immutable data. Use when writing logic or data transformations.
diagnosing-bugs
by mattpocock
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
duplicate-sweep
by superset-sh
Find and merge duplicate Linear issues — group reports of the same underlying bug, pick the survivor, and move the evidence across. Use when the backlog has grown noisy, someone asks whether an issue is already reported, or you are cleaning up before planning.
patch-notes
by Donchitos
"Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication."
hotfix
by Donchitos
"Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly."
bug-report
by Donchitos
"Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context."
changelog
by Donchitos
"Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions."
diagnose
by mattpocock
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
caveman
by microsoft
'Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules'
telemetry-foundations
by microsoft
'Declarative OpenTelemetry-aligned telemetry vocabulary and instrumentation conventions for traces, metrics, logs, and PII handling'