home/categories/debugging
category focus

Debugging

Tools for finding and fixing code issues.

4271 スキルall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
98

interaction-latency

Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.

nexus-labs-automation
nexus-labs-automation
tools
open
debugging
98

instrumentation-planning

Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"

nexus-labs-automation
nexus-labs-automation
tools
open
debugging
98

symbolication-setup

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

nexus-labs-automation
nexus-labs-automation
tools
open
debugging
98

session-context-manager

Manage session lifecycle, memory state, and context windows. Use when starting sessions, checking memory health, optimizing tokens, or understanding session state. Keywords: session start, memory health, context, compact, token usage, circuit breaker

sane-apps
sane-apps
tools
open
debugging
98

session-replay

Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.

nexus-labs-automation
nexus-labs-automation
tools
open
debugging
96

root-cause-tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

tilework-tech
tilework-tech
tools
open
debugging
96

creating-debug-tests-and-iterating

Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.

tilework-tech
tilework-tech
tools
open
debugging
96

flow-debugging

4-phase systematic debugging for flow-fix. NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.

Dimon94
Dimon94
tools
open
debugging
94

wp-performance

Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.

Automattic
Automattic
tools
open
debugging
93

browser

Control a Chromium browser via CDP. Use when automating web browsing, scraping pages, testing web apps, monitoring network traffic, or interacting with page elements.

camhahu
camhahu
tools
open
debugging
93

performance-optimization

Optimize application performance through code splitting, lazy loading, caching strategies, bundle size reduction, render optimization, and profiling. Use when improving page load times, reducing bundle sizes, optimizing React rendering, implementing code splitting, configuring caching strategies, lazy loading components and routes, optimizing images and assets, profiling performance bottlenecks, implementing virtual scrolling for large lists, or improving Core Web Vitals and Lighthouse scores.

korallis
korallis
tools
open
debugging
93

root-cause-tracing

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.

korallis
korallis
tools
open
debugging
93

debugging-systematic

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.

korallis
korallis
tools
open
debugging
90

antipattern-catalog

Document technical debt, anti-patterns, and patterns to avoid from analyzed frameworks. Use when (1) creating a "Do Not Repeat" list from framework analysis, (2) categorizing observed code smells and issues, (3) assessing severity of architectural problems, (4) generating remediation suggestions, or (5) synthesizing lessons learned across multiple frameworks.

aiskillstore
aiskillstore
tools
open
debugging
90

explain-expert

Analyze codebases and provide technical overviews covering core components, interactions, deployment architecture, and runtime behavior. Use when the user asks for codebase analysis, project overview, technical architecture explanation, or system documentation.

aiskillstore
aiskillstore
tools
open
debugging
90

wp-performance

WordPress performance optimization - Core Web Vitals, image/video compression, caching, asset optimization, and speed testing. Use when optimizing site speed or diagnosing performance issues.

aiskillstore
aiskillstore
tools
open
debugging
90

module-health

Modular architecture health assessor for Logseq Template Graph. Analyzes module balance, cohesion, size distribution, and dependencies. Calculates health scores and suggests reorganization. Use when checking module structure, assessing architecture quality, or planning refactoring.

aiskillstore
aiskillstore
tools
open
debugging
90

codebase-explorer

Explore and understand the Empathy Ledger codebase architecture, data flows, database schema, services, and how components connect. Use when you need to understand where things are, how data flows, or how different parts of the system relate to each other.

aiskillstore
aiskillstore
tools
open
debugging
90

technical-research

Technical spike and research investigation specialist. Use when exploring options for a technical decision, conducting timeboxed investigations, or evaluating technology choices.

aiskillstore
aiskillstore
tools
open
debugging
90

ux-audit

Perform comprehensive UX audits on pages, components, or features. Use when the user asks to "audit UX", "review usability", "evaluate the interface", "UX review", or wants a systematic evaluation of user experience quality.

aiskillstore
aiskillstore
tools
open
debugging
90

performance-profiler

Identifies performance bottlenecks including N+1 queries, inefficient loops, memory leaks, and slow algorithms. Use when user mentions performance issues, slow code, optimization, or profiling.

aiskillstore
aiskillstore
tools
open
debugging
90

accessibility-check

Evaluate accessibility and WCAG compliance of UI components and pages. Use when the user asks to "check accessibility", "audit a11y", "WCAG review", "screen reader test", or needs to verify inclusive design practices.

aiskillstore
aiskillstore
tools
open
debugging
90

performance

Comprehensive performance specialist covering analysis, optimization, load testing, and framework-specific performance. Use when identifying bottlenecks, optimizing code, conducting load tests, analyzing Core Web Vitals, fixing memory leaks, or improving application performance across all layers (application, database, frontend). Includes React-specific optimization patterns.

aiskillstore
aiskillstore
tools
open
Previous
Page 65 / 178
Next