hiddenroom-supabase
Specialized Supabase assistant for database migrations, RLS security, and edge function deployment.
Install
mkdir -p .claude/skills/hiddenroom-supabase && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13360" && unzip -o skill.zip -d .claude/skills/hiddenroom-supabase && rm skill.zipInstalls to .claude/skills/hiddenroom-supabase
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Hidden Room Supabase backend skill for migrations, generated database types, Edge Functions, RLS policies, auth/profile sync, storage buckets, Stripe integration, cloud_jobs, and database documentation. Use when editing supabase/migrations, supabase/functions, database.types.ts, or Supabase-backed frontend queries.Key capabilities
- →Inspect existing migrations before adding new ones.
- →Keep browser code using anon/publishable keys only.
- →Enforce RLS as the real authorization boundary.
- →Update or regenerate database.types.ts after schema changes.
- →Deploy Edge Functions only after local review and syntax checks.
- →Document required secrets in docs, not in source code.
How it works
This skill manages Supabase backend workflows by enforcing conventions for migrations, Edge Functions, RLS policies, and type generation, ensuring secure and consistent database operations.
Inputs & outputs
When to use hiddenroom-supabase
- →Running database migrations
- →Deploying edge functions
- →Updating database types
About this skill
Hidden Room Supabase
Workflow
- Inspect existing migrations before adding a new timestamped migration.
- Keep browser code using anon/publishable keys only; use service role only in Edge Functions or the Debian agent.
- Keep RLS as the real authorization boundary.
- Update or regenerate
supabase/database.types.tsand rootdatabase.types.tsafter schema changes when possible. - Deploy Edge Functions only after local review and syntax checks.
- Document required secrets in docs, not in source code.
Backend Layout
- Migrations:
supabase/migrations/*.sql. - Edge Functions:
supabase/functions/*/index.ts. - Config:
supabase/config.toml. - Schema/type snapshots:
supabase/db-*.txt,supabase/database.types.ts, rootdatabase.types.ts. - Operational docs:
docs/store-setup.md,docs/cloud-agent-installation.md.
Edge Function Conventions
- Use
Deno.serve. - Return JSON through a small
json()helper with CORS headers. - Handle
OPTIONSexplicitly. - Validate method, auth token, body shape, quantities, paths, and IDs before database writes.
- Use Supabase service role only after authenticating/authorizing the caller.
References
Read references/supabase-map.md when changing schema, RLS, storage, or functions.
When not to use it
- →When the task does not involve Supabase backend workflows.
- →When the task requires using service role keys directly in browser code.
- →When the task involves bypassing RLS for authorization.
Limitations
- →It requires using Deno.serve for Edge Functions.
- →It requires returning JSON through a small json() helper with CORS headers for Edge Functions.
- →It requires validating method, auth token, body shape, quantities, paths, and IDs before database writes in Edge Functions.
How it compares
This skill provides a structured workflow for Supabase development with specific conventions for security and consistency, unlike ad-hoc development which might lead to vulnerabilities or inconsistencies.
Compared to similar skills
hiddenroom-supabase side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| hiddenroom-supabase (this skill) | 0 | 1mo | No flags | Intermediate |
| prisma-connection-pool-exhaustion | 1 | 6mo | Review | Intermediate |
| backend-patterns | 0 | 1mo | No flags | Advanced |
| backend-dev | 1 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
prisma-connection-pool-exhaustion
blader
Fix Prisma "Too many connections" and connection pool exhaustion errors in serverless environments (Vercel, AWS Lambda, Netlify). Use when: (1) Error "P2024: Timed out fetching a new connection from the pool", (2) PostgreSQL "too many connections for role", (3) Database works locally but fails in production serverless, (4) Intermittent database timeouts under load.
backend-patterns
chenqin231
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
backend-dev
marmelab
Coding practices for backend development in Atomic CRM. Use when deciding whether backend logic is needed, or when creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs.
web-server-architecture
develsvai
`web/src/server/**`의 router, service, 공통 계층을 건드릴 때 사용하는 스킬이다. tRPC router와 service 책임 분리, 도메인 구조, Prisma 사용 경계를 맞춘다.
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
event-store-design
wshobson
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.