01
Design Postgres changes
Create tables, constraints, indexes, functions, triggers, views, extensions, migrations, seeds, and generated application types.
Supabase application development
CategorySoftware Development
Supabase Codex Skills
Supabase Codex Skills help Codex build with Postgres, Auth, Storage, Realtime, Edge Functions, and the Supabase CLI. Download the skills for schema design, migrations, row-level security, generated types, local stacks, seed data, function testing, environment management, and controlled deployment.
SupabasePostgresRow-level securityEdge Functions
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete supabase application development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A Supabase feature is unsafe when the client works but row-level security is incomplete, migration history drifts, service keys leak, or local assumptions do not match the linked project.
A dependable Supabase workflow keeps schema changes in migrations, tests them locally, generates matching types, and treats authorization policies as part of the data model.
These skills help Codex distinguish local and linked commands, preserve secrets, and verify database, Auth, Storage, Realtime, and function behavior together.
What the downloadable skills can do
What Supabase Codex Skills can help accomplish
02
Implement authorization
Write and test row-level security policies, Auth flows, role behavior, service operations, storage policies, and tenant boundaries.
03
Build platform functions
Develop and test Edge Functions, webhooks, scheduled work, Realtime behavior, file operations, and typed client integrations.
04
Manage local-to-remote delivery
Start the local stack, diff and reset migrations, pull deliberate remote history, check status, push approved changes, and deploy functions.
A repeatable working process
How the supabase application development workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Inspect the existing Supabase layout
Read config, migrations, schemas, seed data, generated types, clients, policies, functions, environments, and CLI version.
02
Define data and access invariants
State who can read or change each row or object, required constraints, API behavior, failure modes, and migration compatibility.
03
Build and test locally
Create migrations and policies, reset the local database, seed representative users and data, run functions, and verify typed clients.
04
Review the linked change
Compare migration histories, inspect diffs and destructive operations, regenerate types, then prepare a controlled database and function deployment.
Useful across real projects
Where Supabase Codex Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Database applications
Model relational data, queries, indexes, constraints, functions, migrations, and generated types.
Authentication and authorization
Implement providers, sessions, claims, row-level security, roles, account flows, and tenant isolation.
Functions and integrations
Develop Edge Functions, webhooks, external APIs, background jobs, email, payments, and server-only logic.
Storage and Realtime
Manage buckets, object policies, uploads, signed access, database changes, subscriptions, and presence.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create a Supabase migration
02Write RLS policies
03Generate TypeScript types
04Set up local seed data
05Build an Edge Function
06Debug Auth behavior
07Manage storage access
08Prepare a Supabase deployment
Who benefits most
Who Is This For?
These skills are designed for people who need dependable supabase application development work with a visible process.
Full-stack developers
Build database-backed products with typed clients and explicit authorization.
Startup teams
Move quickly while keeping migrations, secrets, policies, and production changes reviewable.
Backend engineers
Design Postgres behavior, functions, integrations, performance, and operational checks.
Security-conscious teams
Test tenant isolation, roles, storage access, service keys, and policy coverage.
Good to know:
The skills do not reveal project secrets, weaken row-level security for convenience, or run destructive linked-database commands without explicit environment confirmation and approval.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download the Supabase skill folder
Keep database, Auth, RLS, Storage, Realtime, function, and deployment guidance together.
Install it in the application repository
Project scope lets the workflow read Supabase config, migrations, clients, types, and test commands.
Describe local and hosted environments
Record CLI version, project layout, approved linked targets, secrets handling, Auth providers, and deployment controls.
Add data and access checks
List reset, migration, lint, type generation, policy tests, function tests, application tests, and deployment review steps.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Can the skills write Supabase migrations?+
Yes. They create reviewable SQL migrations and test them through the project’s local workflow.
Do they handle row-level security?+
Yes. Policies are designed from explicit user, role, tenant, and operation requirements and tested with representative identities.
Can they build Edge Functions?+
Yes, including local serving, environment access, validation, external APIs, tests, and deployment preparation.
Will they use the service role key in frontend code?+
No. Privileged keys belong only in approved server-side secret storage.
Can they push changes to a hosted project?+
Only after the target, migration history, diff, destructive effects, tests, and authorization are confirmed.
Make the work repeatable
Give Codex a Supabase workflow where schema, policy, types, local tests, and hosted changes remain synchronized.
Clear context. Purposeful work. Relevant checks. A result others can understand.