Agent skill

Fullstack Debugger

by curiositech in curiositech/some_claude_skills

Expert debugger for Next.js + Cloudflare Workers + Supabase stacks.

MITAuto-check: notesBackend & APIs

Install Fullstack Debugger

skills CLI
$ npx skills add curiositech/some_claude_skills --skill fullstack-debugger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install curiositech/some_claude_skills fullstack-debugger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fullstack-debugger .claude/skills/fullstack-debugger && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fullstack-debugger
GitHub stars
243
Token cost
~3.7k tokens
SKILL.md length
433 words
Files
8 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Expert debugger for Next.js + Cloudflare Workers + Supabase stacks.

  • Works in 10 steps: RLS Policy Blocking Data (Most Common!) → CORS Errors → Auth State Not Persisting → …
  • Tasks that involve Caching
  • SKILL.md covers Activation Triggers, Debug Philosophy, Architecture Layers and Quick Diagnosis Commands, plus 5 more sections
  • Runs Shell and JavaScript scripts from its folder; calls npx, npm and curl; reaches api.cloudflare.com; needs NEXT_PUBLIC_SUPABASE_ANON_KEY

What it does

Fullstack Debugger is an agent skill from curiositech/some_claude_skills. Expert debugger for Next.js + Cloudflare Workers + Supabase stacks. Systematic troubleshooting for auth, caching, workers, RLS, CORS, and build issues. Activate on: 'debug', 'not working', 'error', 'broken', '500', '401', '403', 'cache issue', 'RLS', 'CORS'. NOT for: feature development (use language skills), architecture design (use system-architect).

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `.claude-plugin/plugin.json`, `references/debug-decision-tree.md` and `references/error-patterns.md`).

It sits in Backend & APIs, covering Caching. It works with Supabase, Cloudflare Workers and Next.js. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.

When your agent uses it

  • Tasks that involve Caching

Example prompts

  • “not working”
  • “broken”
  • “cache issue”
  • “/fullstack-debugger”

Requirements

  • Node.js
  • A Bash shell
  • A credential in YOUR_ANON_KEY
  • A credential in YOUR_TOKEN
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob, WebFetch, mcp__supabase__*, mcp__playwright__*

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. RLS Policy Blocking Data (Most Common!)
  2. CORS Errors
  3. Auth State Not Persisting
  4. Hydration Mismatch
  5. Worker Not Deploying
  6. TypeScript Cache Haunting
  7. Static Export Issues
  8. Rate Limiting Issues
  9. Meeting/Location Data Issues
  10. Build Fails on Cloudflare Pages

What it can do on your machine

Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Grep
    • Glob
    • WebFetch
    • mcp__supabase__*
    • mcp__playwright__*

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Shell and JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • npm
    • curl
    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.cloudflare.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • NEXT_PUBLIC_SUPABASE_ANON_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fullstack Debugger loads about 3.7k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch, mcp__supabase__*, mcp__playwright__*

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 433 words, ~3,707 tokens.

Download SKILL.mdSave it as .claude/skills/fullstack-debugger/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
fullstack-debugger
description
Expert debugger for Next.js + Cloudflare Workers + Supabase stacks. Systematic troubleshooting for auth, caching, workers, RLS, CORS, and build issues. Activate on: 'debug', 'not working', 'error', 'broken', '500', '401', '403', 'cache issue', 'RLS', 'CORS'. NOT for: feature development (use language skills), architecture design (use system-architect).
allowed-tools
Read, Write, Edit, Bash, Grep, Glob, WebFetch, mcp__supabase__*, mcp__playwright__*
metadata.category
Code Quality & Testing
metadata.tags
debugging, nextjs, cloudflare-workers, supabase, troubleshooting

Fullstack Debugger

Expert debugger for modern web stacks: Next.js 15, Cloudflare Workers, Supabase, and edge deployments. Systematic, evidence-based troubleshooting.

Activation Triggers

Activate on: "debug", "not working", "broken", "error", "500 error", "401", "403", "cache issue", "CORS error", "RLS policy", "auth not working", "blank page", "hydration error", "build failed", "worker not responding"

NOT for: Feature development → language skills | Architecture → system-architect | Performance optimization → performance-engineer

Debug Philosophy

1. REPRODUCE → Can you make it fail consistently?
2. ISOLATE   → Which layer is broken?
3. EVIDENCE  → What do logs/network/state show?
4. HYPOTHESIZE → What could cause this?
5. TEST      → Validate one hypothesis at a time
6. FIX       → Minimal change that resolves issue
7. VERIFY    → Confirm fix doesn't break other things

Architecture Layers

┌─────────────────────────────────────────────────────────────┐
│                    DEBUGGING LAYERS                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Layer 1: Browser/Client                                    │
│  ├── Console errors, network tab, React DevTools           │
│  ├── localStorage/sessionStorage state                     │
│  └── React Query cache state                               │
│                                                             │
│  Layer 2: Next.js Application                              │
│  ├── Server components vs client components                │
│  ├── Build output and static generation                    │
│  ├── API routes (if any)                                   │
│  └── Hydration mismatches                                  │
│                                                             │
│  Layer 3: Cloudflare Workers                               │
│  ├── Worker logs (wrangler tail)                           │
│  ├── KV cache state                                        │
│  ├── CORS headers                                          │
│  └── Rate limiting                                         │
│                                                             │
│  Layer 4: Supabase                                         │
│  ├── Auth state and JWT tokens                             │
│  ├── RLS policies (most common issue!)                     │
│  ├── Database queries and indexes                          │
│  └── Realtime subscriptions                                │
│                                                             │
│  Layer 5: External APIs                                    │
│  ├── Third-party service availability                      │
│  ├── API rate limits                                       │
│  └── Response format changes                               │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Quick Diagnosis Commands

Check Everything At Once
bash
# Run from next-app/ directory
echo "=== Build Check ===" && npm run build 2>&1 | tail -20
echo "=== TypeScript ===" && npx tsc --noEmit 2>&1 | head -20
echo "=== Lint ===" && npm run lint 2>&1 | head -20
echo "=== Git Status ===" && git status --short
Supabase RLS Diagnosis
bash
# Check if RLS is blocking queries (most common issue!)
node -e "
const { createClient } = require('@supabase/supabase-js');
const supabase = createClient(
  'YOUR_SUPABASE_URL',
  'YOUR_ANON_KEY'
);

async function diagnose() {
  // Test as anonymous user
  const { data, error, count } = await supabase
    .from('YOUR_TABLE')
    .select('*', { count: 'exact' })
    .limit(5);

  console.log('Error:', error);
  console.log('Count:', count);
  console.log('Sample:', data);
}
diagnose();
"
Worker Health Check
bash
# Check if workers are responding
curl -s -o /dev/null -w "%{http_code}" https://YOUR-WORKER.workers.dev/health

# Check CORS headers
curl -s -D - -o /dev/null -H "Origin: https://yoursite.com" \
  https://YOUR-WORKER.workers.dev/api/endpoint | grep -iE "(access-control|x-)"

# Stream worker logs
cd workers/your-worker && npx wrangler tail
Cache Inspection
bash
# Check Cloudflare KV cache
npx wrangler kv:key list --namespace-id=YOUR_NAMESPACE_ID | head -20

# Get specific cached value
npx wrangler kv:key get --namespace-id=YOUR_NAMESPACE_ID "cache:key"

# Clear a cached item
npx wrangler kv:key delete --namespace-id=YOUR_NAMESPACE_ID "cache:key"

Common Issues & Solutions

1. RLS Policy Blocking Data (Most Common!)

Symptoms:

  • Query returns empty array but no error
  • Works in Supabase dashboard but not in app
  • Works for some users but not others

Diagnosis:

sql
-- In Supabase SQL Editor
-- Check what policies exist
SELECT schemaname, tablename, policyname, permissive, roles, cmd, qual
FROM pg_policies
WHERE tablename = 'your_table';

-- Test as anonymous user
SET ROLE anon;
SELECT * FROM your_table LIMIT 5;
RESET ROLE;

-- Test as authenticated user
SET ROLE authenticated;
SET request.jwt.claims = '{"sub": "user-uuid-here"}';
SELECT * FROM your_table LIMIT 5;
RESET ROLE;

Common Fixes:

sql
-- Allow public read access
CREATE POLICY "Allow public read" ON your_table
  FOR SELECT USING (true);

-- Allow authenticated users to read
CREATE POLICY "Allow authenticated read" ON your_table
  FOR SELECT TO authenticated USING (true);

-- Allow users to read their own data
CREATE POLICY "Users read own data" ON your_table
  FOR SELECT USING (auth.uid() = user_id);
2. CORS Errors

Symptoms:

  • "Access to fetch blocked by CORS policy"
  • Works in Postman but not in browser
  • Preflight request fails

Diagnosis:

bash
# Check what CORS headers are returned
curl -s -D - -o /dev/null \
  -H "Origin: https://yoursite.com" \
  -H "Access-Control-Request-Method: POST" \
  -X OPTIONS \
  https://your-worker.workers.dev/api/endpoint

Fix in Cloudflare Worker:

typescript
// In your worker
const corsHeaders = {
  'Access-Control-Allow-Origin': '*', // Or specific domain
  'Access-Control-Allow-Methods': 'GET, POST, OPTIONS',
  'Access-Control-Allow-Headers': 'Content-Type, Authorization',
};

// Handle preflight
if (request.method === 'OPTIONS') {
  return new Response(null, { headers: corsHeaders });
}

// Add to all responses
return new Response(data, {
  headers: { ...corsHeaders, 'Content-Type': 'application/json' }
});
3. Auth State Not Persisting

Symptoms:

  • User logged in but shows as logged out on refresh
  • Auth works locally but not in production
  • Session disappears randomly

Diagnosis:

javascript
// In browser console
console.log('Session:', await supabase.auth.getSession());
console.log('User:', await supabase.auth.getUser());
console.log('LocalStorage:', Object.keys(localStorage).filter(k => k.includes('supabase')));

Common Fixes:

  • Check Supabase URL matches (http vs https, trailing slash)
  • Verify site URL in Supabase Auth settings
  • Check for cookie blocking (Safari, incognito)
  • Ensure AuthContext wraps all components needing auth
4. Hydration Mismatch

Symptoms:

  • "Hydration failed because the initial UI does not match"
  • Content flashes on page load
  • Different content on server vs client

Diagnosis:

typescript
// Temporarily add to suspect component
useEffect(() => {
  console.log('Client render:', document.body.innerHTML.slice(0, 500));
}, []);

Common Fixes:

typescript
// Use client-only rendering for dynamic content
'use client';
import { useState, useEffect } from 'react';

function DynamicContent() {
  const [mounted, setMounted] = useState(false);
  useEffect(() => setMounted(true), []);
  if (!mounted) return null; // or skeleton
  return <div>{/* dynamic content */}</div>;
}
5. Worker Not Deploying

Symptoms:

  • Deploy command succeeds but changes not reflected
  • Old code still running
  • Intermittent old/new behavior

Diagnosis:

bash
# Check deployment status
npx wrangler deployments list

# View current worker code
npx wrangler deployments view

# Check for multiple environments
npx wrangler whoami

Fixes:

bash
# Force redeploy
npx wrangler deploy --force

# Clear Cloudflare cache
curl -X POST "https://api.cloudflare.com/client/v4/zones/ZONE_ID/purge_cache" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"purge_everything":true}'
6. TypeScript Cache Haunting

Symptoms:

  • Errors reference deleted/changed code
  • Types don't match current code
  • "Cannot find module" for existing files

Fix:

bash
# Nuclear option - clear all caches
rm -rf .next node_modules/.cache tsconfig.tsbuildinfo
npm run build

# Or just TypeScript cache
rm -rf node_modules/.cache/typescript
npx tsc --build --clean
Show full SKILL.md (164 more words)Show less
7. Static Export Issues

Symptoms:

  • "Error: Page X couldn't be rendered statically"
  • Dynamic routes fail in static export
  • API routes don't work after deploy

Diagnosis:

bash
# Check next.config for output mode
grep -A5 "output:" next.config.ts

# Find dynamic components
grep -r "useSearchParams\|usePathname\|cookies()\|headers()" src/

Fixes:

typescript
// For components using dynamic APIs
export const dynamic = 'force-dynamic';
// or wrap in Suspense with fallback

// For generateStaticParams
export async function generateStaticParams() {
  return [{ slug: 'page1' }, { slug: 'page2' }];
}
8. Rate Limiting Issues

Symptoms:

  • 429 errors after several requests
  • Works initially then stops
  • Different behavior per IP

Diagnosis:

bash
# Check rate limit headers
curl -i https://your-worker.workers.dev/api/endpoint 2>&1 | grep -i ratelimit

# Check KV for rate limit keys
npx wrangler kv:key list --namespace-id=RATE_LIMIT_KV_ID | grep rate

Fixes:

bash
# Clear rate limit for an IP
npx wrangler kv:key delete --namespace-id=RATE_LIMIT_KV_ID "rate:192.168.1.1"

# Adjust limits in wrangler.toml
RATE_LIMIT_REQUESTS = "100"
RATE_LIMIT_WINDOW = "3600"
9. Meeting/Location Data Issues

Symptoms:

  • No meetings found in certain areas
  • Stale meeting data
  • Cache showing wrong data

Diagnosis:

bash
# Check cache status for a location
curl -s -D - -o /dev/null \
  -H "Origin: https://yoursite.com" \
  "https://your-proxy.workers.dev/api/all?lat=45.52&lng=-122.68&radius=25" \
  | grep -iE "(x-cache|x-geohash|x-source)"

# Force cache refresh
curl -H "Origin: https://yoursite.com" \
  "https://your-proxy.workers.dev/warm"

# Check Supabase for meeting count
node -e "
const { createClient } = require('@supabase/supabase-js');
const supabase = createClient('URL', 'KEY');
supabase.from('meetings').select('*', { count: 'exact', head: true })
  .then(({count}) => console.log('Total meetings:', count));
"
10. Build Fails on Cloudflare Pages

Symptoms:

  • Works locally but fails on deploy
  • "Module not found" errors
  • Memory exceeded

Diagnosis:

bash
# Check build output locally
NODE_ENV=production npm run build 2>&1 | tee build.log

# Check for conditional imports
grep -r "require(" src/ --include="*.ts" --include="*.tsx"

# Check bundle size
npx next-bundle-analyzer

Fixes:

javascript
// next.config.ts - increase memory
module.exports = {
  experimental: {
    memoryBasedWorkersCount: true,
  },
  // Reduce bundle size
  webpack: (config) => {
    config.externals = [...(config.externals || []), 'sharp'];
    return config;
  }
};

Debug Scripts

scripts/diagnose.sh
bash
#!/bin/bash
# Run all diagnostics

echo "=== Environment ==="
node -v && npm -v

echo "=== Dependencies ==="
npm ls --depth=0 2>&1 | grep -E "(UNMET|missing)"

echo "=== TypeScript ==="
npx tsc --noEmit 2>&1 | head -30

echo "=== Build ==="
npm run build 2>&1 | tail -30

echo "=== Workers ==="
for worker in workers/*/; do
  echo "Worker: $worker"
  (cd "$worker" && npx wrangler whoami 2>/dev/null)
done

echo "=== Supabase ==="
npx supabase status 2>/dev/null || echo "Supabase CLI not configured"
scripts/check-rls.js
javascript
// Check RLS policies are working correctly
const { createClient } = require('@supabase/supabase-js');

const supabase = createClient(
  process.env.NEXT_PUBLIC_SUPABASE_URL,
  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY
);

async function checkTable(table) {
  console.log(`\n=== Checking ${table} ===`);
  const { data, error, count } = await supabase
    .from(table)
    .select('*', { count: 'exact' })
    .limit(1);

  if (error) {
    console.log(`ERROR: ${error.message}`);
  } else {
    console.log(`OK: ${count} rows accessible`);
  }
}

// Check critical tables
['profiles', 'meetings', 'forum_posts', 'journal_entries'].forEach(checkTable);

Validation Checklist

[ ] Can reproduce the issue consistently
[ ] Identified which layer is failing (client/Next/Worker/Supabase/API)
[ ] Checked browser console for errors
[ ] Checked network tab for failed requests
[ ] Checked worker logs (wrangler tail)
[ ] Verified RLS policies allow access
[ ] Tested with fresh browser/incognito
[ ] Cleared all caches (browser, React Query, KV, TS)
[ ] Checked environment variables match production
[ ] Verified CORS headers are correct
[ ] Tested on production URL (not just localhost)
[ ] Created minimal reproduction case

Output

When debugging, always provide:

  1. Root cause - What exactly was wrong
  2. Evidence - Logs, errors, or queries that proved it
  3. Fix - Minimal code change to resolve
  4. Verification - How to confirm it's fixed
  5. Prevention - How to avoid this in future

Tools Available

  • Read, Write, Edit - File operations
  • Bash - Run commands, curl, wrangler
  • Grep, Glob - Search codebase
  • WebFetch - Test endpoints
  • mcp__supabase__* - Direct Supabase operations
  • mcp__playwright__* - Browser automation for UI testing

© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references) in .claude/skills/fullstack-debugger of curiositech/some_claude_skills.

  • SKILL.md
  • .claude-plugin/plugin.json
  • references/debug-decision-tree.md
  • references/error-patterns.md
  • scripts/check-cors.sh
  • scripts/check-rls.js
  • scripts/diagnose.sh
  • scripts/inspect-cache.sh

Open the folder on GitHubat commit 6713fc7

Compare with similar skills

Fullstack Debugger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fullstack Debugger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fullstack Debugger this skillcuriositech/some_claude_skills243—~3.7kAutomated safety check: NotesMIT
Cloudflare Nextjssecondsky/claude-skills227—~5.3kAutomated safety check: NotesMIT
Olore Opennext Latestolorehq/olore103—~825Automated safety check: PassMIT
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Supabasecurvenote/curvenote1695 repos~2.2kAutomated safety check: PassCustom licence
Yalidine Delivery Integrationbighadj22/codflow343—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Cloudflare Nextjs

    secondsky/claude-skills

    Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare).

    227 GitHub stars~5.3k tokensUpdated 9 days ago
    Backend & APIsAuto-check: notes
  • Local opennext documentation reference (latest). An agent skill from olorehq/olore.

    103 GitHub stars~825 tokensUpdated today
    Backend & APIsAuto-check passed
  • Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    169 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • Wires an app to the Yalidine (Guepex) Algerian courier API: parcels, zone lookups, delivery fees and verified delivery-status webhooks.

    343 GitHub stars~2.5k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Spiceflow

    remorses/spiceflow

    Spiceflow is a super simple, fast, and type-safe API and React Server Components framework for TypeScript.

    167 GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed

More from curiositech/some_claude_skills

All 108 skills in this repo
  • Crisis Detection Intervention AI

    curiositech/some_claude_skills

    Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.

    243 GitHub starsUsed in 3 repos~3.8k tokens
    Auto-check passed
  • Form Validation Architect

    curiositech/some_claude_skills

    End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.

    243 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Competitive Cartographer

    curiositech/some_claude_skills

    Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.

    243 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • GitHub Actions Pipeline Builder

    curiositech/some_claude_skills

    Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

    243 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check: notes
  • Computer Vision Pipeline

    curiositech/some_claude_skills

    Build production computer vision pipelines for object detection, tracking, and video analysis.

    243 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Design Archivist

    curiositech/some_claude_skills

    Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…

    243 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Categories

Questions about Fullstack Debugger

What does Fullstack Debugger do?

Expert debugger for Next.js + Cloudflare Workers + Supabase stacks. Fullstack Debugger is an agent skill from curiositech/some_claude_skills.js + Cloudflare Workers + Supabase stacks.

When should I use Fullstack Debugger?

Fullstack Debugger fits situations like: tasks that involve Caching.

How do I install Fullstack Debugger in Claude Code?

Run `npx skills add curiositech/some_claude_skills --skill fullstack-debugger -a claude-code`. Or copy the skill folder (.claude/skills/fullstack-debugger in curiositech/some_claude_skills) into .claude/skills/fullstack-debugger in your project. Claude Code loads it when a task matches its description.

How do I install Fullstack Debugger in Codex?

Run `npx skills add curiositech/some_claude_skills --skill fullstack-debugger -a codex`. Or copy the skill folder (.claude/skills/fullstack-debugger in curiositech/some_claude_skills) into .agents/skills/fullstack-debugger in your project. Codex loads it when a task matches its description.

Can I use Fullstack Debugger in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill fullstack-debugger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fullstack-debugger, .gemini/skills/fullstack-debugger, .github/skills/fullstack-debugger and .opencode/skills/fullstack-debugger in your project.

What does Fullstack Debugger need to run?

Going by SKILL.md and its folder, Fullstack Debugger needs a shell and JavaScript for the scripts in its folder, the command-line tools its instructions call (npx, npm, curl, node and git) and credentials named NEXT_PUBLIC_SUPABASE_ANON_KEY. Our summary lists: Node.js; A Bash shell; A credential in YOUR_ANON_KEY; A credential in YOUR_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch, mcp__supabase__*, mcp__playwright__*.

Does Fullstack Debugger access the network?

SKILL.md names 1 domain. In commands or code: api.cloudflare.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Fullstack Debugger safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Fullstack Debugger use?

Fullstack Debugger is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fullstack Debugger use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Fullstack Debugger?

Skills that share tags, products or a category with Fullstack Debugger: Cloudflare Nextjs (secondsky/claude-skills, 227 stars), Olore Opennext Latest (olorehq/olore, 103 stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars) and Supabase (curvenote/curvenote, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fullstack Debugger?

curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 6, 2026.

Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.