Menu
Use when changing Supabase schema, adding columns, backfills, or production migrations that must not break existing apps. Not for client-only UI or seed data in local dev only.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
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 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 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.
Baseado na classificação ocupacional SOC
| name | migration-playbook |
| description | Use when changing Supabase schema, adding columns, backfills, or production migrations that must not break existing apps. Not for client-only UI or seed data in local dev only. |
20240522_add_posts_status.sql.ALTER TABLE public.posts ADD COLUMN status text DEFAULT 'draft';
-- backfill if needed
UPDATE public.posts SET status = 'draft' WHERE status IS NULL;
-- then NOT NULL if required, in later migration
If unavoidable:
DROP COLUMN on day one of rename.