Menu
Use when standardizing API and edge function errors: HTTP status codes, error JSON shape, logging, or mapping Supabase/Stripe errors to client responses. Not for UI toast copy only or form field validation messages.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when reviewing or fixing accessibility: keyboard navigation, focus order, labels, color contrast, screen reader support, or ARIA attributes. Not for SEO-only or performance-only audits.
Use when adding product analytics (PostHog, GA4, Plausible), event tracking, funnels, or conversion measurement. Not for server logs only or A/B infra unless events are part of the task.
Use when recording audit trails: who changed what, admin action logs, compliance history, or append-only event tables. Not for product analytics (use analytics-events) or debug console logs only.
Use when scheduling background work: cron jobs, digest emails, cleanup tasks, pg_cron, Supabase scheduled edge functions, or job queues. Not for synchronous user-facing API in the request path.
Use when adding dark mode, theme toggle, system theme support, or fixing hardcoded colors that break in dark mode. Not for design-token migration unrelated to dark mode.
Use when building dashboards, charts, KPI cards, trend lines, or analytics UI with Recharts or shadcn's chart components. Not for static landing-page graphics or product analytics tracking (use analytics-events).
| name | api-error-handling |
| description | Use when standardizing API and edge function errors: HTTP status codes, error JSON shape, logging, or mapping Supabase/Stripe errors to client responses. Not for UI toast copy only or form field validation messages. |
Use a consistent JSON body:
{
"error": "forbidden",
"message": "You do not have access to this project."
}
Optional details for validation (api-error-handling + server-input-validation).
| Code | error slug | When |
|---|---|---|
| 400 | invalid_input | Zod / bad params |
| 401 | unauthorized | Missing/invalid JWT |
| 403 | forbidden | Authenticated, not allowed |
| 404 | not_found | Resource hidden or missing |
| 409 | conflict | Unique violation, duplicate |
| 429 | rate_limited | Too many requests |
| 500 | internal_error | Unexpected — generic message to client |
function jsonError(status: number, error: string, message: string) {
return new Response(JSON.stringify({ error, message }), {
status,
headers: { "Content-Type": "application/json" },
});
}
const { error } = await supabase.from("posts").insert(row);
if (error) {
if (error.code === "23505") return jsonError(409, "conflict", "Already exists");
if (error.code === "42501") return jsonError(403, "forbidden", "Not allowed");
console.error(error);
return jsonError(500, "internal_error", "Something went wrong");
}
console.error with correlation id (crypto.randomUUID() in response header x-request-id).Hooks/forms map error slug to toast; show message to users, not raw DB text.
200 with { success: false } for errors.error.message from Postgres in production.catch {} blocks.