supabase-policy-guardrails
Implement Supabase lint rules, policy enforcement, and automated guardrails.Use when setting up code quality rules for Supabase integrations, implementingpre-commit hooks, or configuring CI policy checks for Supabase best practices.Trigger with phrases like "supabase policy", "supabase lint","supabase guardrails", "supabase best practices check", "supabase eslint".
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for implementing Supabase lint rules, policy enforcement, and automated guardrails. It enables developers to automate code quality checks and security policies through ESLint, pre-commit hooks, and CI/CD pipelines, ensuring all Supabase integrations follow industry-leading best practices and security standards.
Use Cases
- Security Policy Enforcement: Automatically implement and verify Row Level Security (RLS) and database policies to protect sensitive data and ensure compliance.
- Automated Linting for Supabase: Integrate custom ESLint rules to detect anti-patterns and enforce consistent coding standards specifically for Supabase-based projects.
- CI/CD Pipeline Guardrails: Set up automated 'policy-as-code' checks in CI/CD workflows to block insecure or non-compliant code changes before they reach production.
- Pre-commit Hook Configuration: Deploy local development hooks that provide immediate feedback to developers, preventing common Supabase configuration errors and secret leaks early in the development cycle.
| name | supabase-policy-guardrails |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npx:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase Policy Guardrails
Prerequisites
- ESLint configured in project
- Pre-commit hooks infrastructure
- CI/CD pipeline with policy checks
- TypeScript for type enforcement
Instructions
Step 1: Create ESLint Rules
Implement custom lint rules for Supabase patterns.
Step 2: Configure Pre-Commit Hooks
Set up hooks to catch issues before commit.
Step 3: Add CI Policy Checks
Implement policy-as-code in CI pipeline.
Step 4: Enable Runtime Guardrails
Add production safeguards for dangerous operations.
Output
- ESLint plugin with Supabase rules
- Pre-commit hooks blocking secrets
- CI policy checks passing
- Runtime guardrails active
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.