advanced-debugging

Debug and troubleshoot issues across the MyJKKN application stack.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Jicate-Solutions/arts_tally_roja --skill advanced-debugging-jicate-solutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-debugging
Source: https://github.com/Jicate-Solutions/arts_tally_roja/tree/main/.claude/skills/advanced-debugging
Command: npx skills add https://github.com/Jicate-Solutions/arts_tally_roja --skill advanced-debugging-jicate-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires next, supabase, react-query, typescript, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides specialized debugging workflows and tools to efficiently troubleshoot issues in the MyJKKN application stack.

Core Features & Use Cases

  • Systematic Workflows: Step-by-step processes for debugging each layer of your application (UI, Service, Database).
  • Common Issues Database: Known issues with tested solutions specific to the MyJKKN stack.
  • Automated Tools: Scripts that analyze project configuration and identify problems.
  • Quick Reference: Fast lookup for common debugging commands and patterns.
  • Use Case: When you encounter a bug, performance issue, or authentication problem in your MyJKKN application, use this Skill to quickly diagnose and fix the issue.

Quick Start

Run the debug-analyzer script to analyze your project configuration and identify potential issues.

Frequently Asked Questions about advanced-debugging

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

FAQPage Schema
How do I debug authentication and performance issues in a Next.js and Supabase application?

Debugging a Next.js and Supabase application involves analyzing project configuration and tracing issues across UI, service, and database layers using automated scripts and systematic workflows to diagnose authentication and performance problems.

What is the best way to troubleshoot React Query and TypeScript issues in my web stack?

The best way to troubleshoot React Query and TypeScript issues is to consult a known issues database with tested solutions, utilizing quick reference commands and automated analysis tools to pinpoint problems in the service layer.

Can I automatically analyze my project configuration to identify problems in a Next.js and TypeScript stack?

Yes, you can run a debug-analyzer script to automatically analyze your Next.js and TypeScript project configuration, which identifies potential issues and provides a systematic approach to fixing them.

Does this debugging workflow support finding known issues specific to the MyJKKN application stack?

Yes, this debugging workflow supports the MyJKKN application stack by providing a common issues database containing known problems with tested solutions specific to Next.js, Supabase, React Query, and TypeScript.

Why do my Supabase service layer calls fail and how can I systematically debug them?

Supabase service layer calls fail due to various configuration or network issues, which you can systematically debug by running automated analysis scripts and following step-by-step processes designed for database and service layer troubleshooting.

When should I use a systematic debugging workflow instead of manual troubleshooting for full-stack issues?

You should use a systematic debugging workflow for full-stack issues when you encounter persistent bugs across Next.js, Supabase, or React Query layers, ensuring comprehensive analysis instead of missing interconnected configuration problems.