Agent skill
supabase-framework
Use for any Supabase database work in PierceDesk, including schema, migrations, RLS, and query patterns. Requires MCP-only database access and references docs/system execution/design guidance.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/supabase-framework
SKILL.md
Supabase Framework Skill
Core rules
- Cloud database only: use Supabase MCP tools for all DB operations.
- No local DB connections (no psql, no DATABASE_URL).
- RLS required: all tables must enforce
auth.uid()or org-scoped policies. - Align schema with existing CRM patterns in docs/system.
Required references (read before DB work)
references/system-docs-map.mdreferences/rls-auth-patterns.md
Operational guidance
- Validate auth context in API routes; DB layer assumes
auth.uid(). - Use migrations and seeds in
database/when applicable. - Prefer indexed columns for frequently filtered fields.
- For large datasets, design queries with pagination + selective columns.
Process checklist
- Identify existing schema and tables in docs/system.
- Use MCP tools to verify current schema.
- Implement migrations or SQL updates via MCP.
- Add/verify RLS policies per table.
- Seed minimal data if required and document changes.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?