Use when a task involves EPDC backend planning or execution for projects that may require Supabase, including form handling, data storage decisions, authentication boundaries, security rules, and migration discipline.
Instalação
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 a task involves EPDC backend planning or execution for projects that may require Supabase, including form handling, data storage decisions, authentication boundaries, security rules, and migration discipline.
Supabase Skill
When To Use
Use this skill when the task involves:
backend form delivery
persistent data decisions
Supabase-backed integrations
authentication or role boundaries
row-level security or data exposure concerns
migration planning for backend scope
Do not use this skill for:
purely static frontend work
content or SEO planning without backend implications
adding a database just because a backend tool exists
Required Context
AGENTS.md
specs/schema.md
the active project specification
the assigned planner task
agents/backend.md when the backend agent contract is in play
frontend task context when public forms or integrations cross the boundary
Instructions
Determine whether backend behavior is actually required by the specification.
Keep launch scope minimal when the project is primarily static.
Add tables or persistent records only for real business needs.
Define authentication only when protected workflows are explicit requirements.
Treat every public form or input as untrusted.
Keep service-role usage off the client when possible.
Use explicit migrations for schema changes.
Document how backend decisions map back to specification requirements.
Surface blocked integrations or missing configuration details explicitly.
Constraints
Do not add a database when launch is static.
Do not add authentication without a real requirement.
Do not broaden backend scope beyond the assigned task.
Do not expose sensitive data through loose client permissions.
Do not treat Supabase as mandatory for every EPDC project.
EPDC Standards
Backend scope must remain proportional to the specification.
Security planning is mandatory whenever Supabase enters scope.
Database design must map directly to planner tasks and specification requirements.
Form submission handling should stay lightweight unless dashboards or persistent workflows are required.
Avoid hidden coupling between frontend structure and backend assumptions.
