Execute diagnose and fix Supabase common errors and exceptions. Use when encountering Supabase errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "supabase error", "fix supabase", "supabase not working", "debug supabase".
From supabase-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin supabase-packThis skill is limited to using the following tools:
references/errors.mdreferences/examples.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Supabase errors typically originate from one of three layers: the PostgREST API layer (HTTP 4xx/5xx responses), the Supabase client SDK (JavaScript exceptions), or the underlying PostgreSQL database (constraint violations, permission denials). Identifying which layer the error comes from narrows your troubleshooting path significantly before you start making changes.
Check error message and code in your logs or console. Note the HTTP status code if the error came from a network request — 401 means authentication failed, 403 means row-level security denied the operation, 409 means a uniqueness constraint was violated, and 500 means the database query itself failed. For SDK errors, check the error.message and error.code properties on the returned error object.
Match your error to one of the documented cases in the references file. Pay attention to whether the error is transient (network timeout, temporary overload) or deterministic (bad credentials, schema mismatch). Transient errors warrant a retry strategy; deterministic errors require a code or configuration fix.
Follow the solution steps for your specific error. After applying a fix, test the exact operation that failed to confirm resolution before closing the issue. If the error recurs intermittently, add structured logging around the Supabase call to capture the full error context for the next occurrence.
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Execute diagnose and fix Supabase common errors and exceptions.