debugging

Guide systematic debugging workflows for frontend and backend applications.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/nakano1122/dotfiles --skill debugging-nakano1122
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/nakano1122/dotfiles/tree/main/dot_agents/skills/debugging
Command: npx skills add https://github.com/nakano1122/dotfiles --skill debugging-nakano1122

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to debugging complex issues across both frontend and backend systems, helping you quickly identify, diagnose, and resolve bugs and performance bottlenecks.

Core Features & Use Cases

  • Systematic Debugging Workflow: Guides you through a structured process from reproduction to verification.
  • Layered Troubleshooting: Offers specific techniques for frontend, backend, and network-related problems.
  • Common Error Patterns: Identifies and provides solutions for frequently encountered errors.
  • Use Case: When a user reports a bug that you cannot immediately reproduce, use this Skill to follow a methodical approach to isolate the problem area and pinpoint the root cause.

Quick Start

Use the debugging skill to help diagnose a slow API response.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to debug a slow API response across the stack?

Debugging a slow API response requires a systematic workflow to isolate the issue layer by layer. This Skill guides you through root cause analysis, helping you pinpoint performance bottlenecks across frontend, backend, and network layers.

How do I isolate a frontend bug when I cannot immediately reproduce it?

To isolate a frontend bug you cannot reproduce, follow a structured debugging workflow from reproduction to verification. This Skill provides methodical troubleshooting techniques to identify common error patterns and pinpoint the root cause.

Does this debugging approach work for both frontend and backend applications?

Yes, this debugging approach is framework-agnostic and works for both frontend and backend applications. It offers specific troubleshooting techniques for isolating errors across different layers of the stack to facilitate root cause analysis.

How do I systematically troubleshoot network and backend performance issues?

Systematically troubleshoot network and backend performance issues by applying layered troubleshooting techniques. This Skill helps identify common error patterns and isolate problem areas to resolve complex bugs methodically.

What are the limitations of a framework-agnostic debugging workflow?

A framework-agnostic debugging workflow provides systematic issue isolation techniques rather than tool-specific automated fixes. It guides root cause analysis for bugs and performance issues, requiring you to apply the structured steps to your specific environment.