debugging
0
investigation-modes
Three explicit investigation modes: LEARNING (build understanding), INVESTIGATION (diagnose problems), SOLVING (implement fixes). Prefix messages with mode, ask before transitioning.
jagreehal
tools
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
0
root-cause-tracing
Systematically trace bugs backward through call stack to find original trigger
DxTa
tools
debugging
0
canvas-debugging
Debug canvas layout issues, grid positioning problems, and component overlap. Use when troubleshooting Konva canvas rendering, grid constraints, snap-to-grid behavior, or visual layout mismatches. Includes Canvas→CSS Grid conversion debugging.
jhlee0409
tools
debugging
0
check-performance
Analyze performance-related HTML issues on web pages. Use when users ask to check page performance, audit resource loading, verify lazy loading, check preload hints, or analyze render-blocking resources. Detects missing optimizations, large resources, render-blocking issues, and Core Web Vitals problems.
leobrival
tools
debugging
0
ui-preview
Preview and screenshot local dev servers URLs. Use when asked to view UI components, take screenshots of or inspect the web/server apps.
thesobercoder
tools
debugging
0
typescript-performance-best-practices
TypeScript performance optimization guidelines for build times, type-checking, declaration emit, and editor responsiveness. This skill should be used when writing, reviewing, or optimizing TypeScript code and tsconfig settings. Triggers on tasks involving slow builds, slow type-checking, CI timeouts, editor lag, tsserver memory issues, monorepo configuration, project references, incremental builds, declaration emit, or any TypeScript performance investigation.
mcart13
tools
debugging
0
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior - requires finding root cause before attempting any fixes
asadullah48
tools
debugging
0
recon-workbench
Analyze and report authorized evidence using Recon Workbench workflows (rwb). Use when running rwb commands.
jscraik
tools
debugging
0
bug-bounty-program
Эксперт по bug bounty. Используй для поиска уязвимостей, написания отчётов, responsible disclosure и penetration testing.
dengineproblem
tools
debugging
0
dev-coding-debug
체계적인 디버깅(Systematic Debugging) 절차를 통해 버그의 원인을 찾고 해결합니다. (Source: obra/superpowers)
lastdays03
tools
debugging
0
browser-automation
This skill should be used when working on frontend code, debugging UI issues, verifying visual changes, scraping web pages, testing web features, or inspecting page state. Also triggers on "open browser", "take screenshot", "navigate to URL", "check cookies", "extract page content", or any web automation task. Use proactively during frontend development to verify changes visually.
tavva
tools
debugging
0
css-inspector
Deep CSS analysis tool for understanding specificity, cascade order, inheritance chains, and computed styles. Visualizes CSS complexity and suggests simplifications. Use when debugging specificity issues or understanding CSS behavior.
andronics
tools
debugging
0
screenshot-analyzer
Analyze screenshots with accurate coordinate mapping for UI debugging and Playwright testing. Use when debugging UI issues from screenshots, creating precise click targets, or implementing visual test automation.
jdeweedata
tools
debugging
0
concurrency-expert
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors.
patrickserrano
tools
debugging
0
graph-query
Query the code graph for callers, dependencies, and blast radius. Use when you need to understand code relationships, find what calls a function, determine impact of changes, or explore the codebase structure.
rollercoaster-dev
tools
debugging
0
notebook-debug
This skill should be used when the user asks to "debug notebook", "inspect notebook outputs", "find notebook error", "read traceback from ipynb", "why did notebook fail", or needs to understand runtime errors in executed Jupyter notebooks from any source (marimo, jupytext, papermill).
edwinhu
tools
debugging
0
phoenix-precision-guard
Precision and type-safety hardening for Phoenix calculation paths. Use when configuring ESLint/TypeScript, replacing parseFloat in P0 files, or validating Decimal.js precision.
nikhillinit
tools
debugging
0
performance-optimization
Performance optimization playbook (measure → diagnose → fix → verify) for this repo (React + R3F + Three.js + Vite). Use when asked to improve FPS, reduce jank, lower draw calls, optimize loading/bundle size, or investigate CPU/GPU/memory bottlenecks.
deadronos
tools
debugging
0
30-analyze-impact-150
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.
MykhailoDmytriakha
tools
debugging
0
ios-simulator-debugger
You are the iOS Simulator runtime debugging specialist.
willsigmon
tools
debugging
0
impact-analysis
コード変更の影響範囲分析スキル。変更が引き起こし得る影響を影響面（code/interface/data/external/config/runtime/security/observability）ごとに整理し、「どこをレビューし、何をテストし、何を観測すべきか」を根拠つきで提示する。 トリガー条件: - 「影響範囲を分析して」「この変更の影響は？」「どこまで波及する？」 - PRレビュー依頼時、リファクタ/仕様変更時 - 障害対応で「原因箇所の周辺影響」を確認したい時 注意: 変更の是非の最終判断は行わない。実行時にしか分からない挙動は推定と不確実性を提示する。
CAPHTECH
tools
debugging
0
selection-data-caching
SUPERSEDED by persistent-cache-gap-filling (v2.8.0). Cache data during symbol selection for instant repeat runs.
smith6jt-cop
tools