supabase-known-pitfalls
Identify and avoid Supabase anti-patterns and common integration mistakes.Use when reviewing Supabase code for issues, onboarding new developers,or auditing existing Supabase integrations for best practices violations.Trigger with phrases like "supabase mistakes", "supabase anti-patterns","supabase pitfalls", "supabase what not to do", "supabase code review".
When & Why to Use This Skill
This Claude skill helps developers identify and eliminate Supabase anti-patterns and common integration mistakes. It streamlines the code review process by auditing existing integrations for security vulnerabilities, performance bottlenecks, and best practice violations, ensuring a robust and scalable Supabase implementation.
Use Cases
- Automated Code Reviews: Scan pull requests for common Supabase pitfalls like improper async/await handling or insecure Row Level Security (RLS) configurations.
- Developer Onboarding: Provide new team members with immediate feedback on their Supabase code to ensure they follow established best practices from day one.
- Security Auditing: Audit existing Supabase projects to detect potential security risks, such as exposed service roles or missing rate limiting.
- Performance Optimization: Identify inefficient query patterns or integration mistakes that could lead to latency or high resource consumption.
| name | supabase-known-pitfalls |
|---|---|
| description | | |
| allowed-tools | Read, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase Known Pitfalls
Prerequisites
- Access to Supabase codebase for review
- Understanding of async/await patterns
- Knowledge of security best practices
- Familiarity with rate limiting concepts
Instructions
Step 1: Review for Anti-Patterns
Scan codebase for each pitfall pattern.
Step 2: Prioritize Fixes
Address security issues first, then performance.
Step 3: Implement Better Approach
Replace anti-patterns with recommended patterns.
Step 4: Add Prevention
Set up linting and CI checks to prevent recurrence.
Output
- Anti-patterns identified
- Fixes prioritized and implemented
- Prevention measures in place
- Code quality improved
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.