supabase-postgres-best-practices
（中文）Supabase Postgres Best Practices
Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.
When to Apply
Reference these guidelines when:
- Writing SQL queries or designing schemas
- Implementing indexes or query optimization
- Reviewing database performance issues
- Configuring connection pooling or scaling
- Optimizing for Postgres-specific features
- Working with Row-Level Security (RLS)
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Query Performance | CRITICAL | query- |
More from jackiexiao/jackie-skills-dev
verification-before-completion
（中文）Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
9using-git-worktrees
（中文）Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
8systematic-debugging
（中文）Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8requesting-code-review
（中文）Use when completing tasks, implementing major features, or before merging to verify work meets requirements
8receiving-code-review
（中文）Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
8test-driven-development
（中文）Use when implementing any feature or bugfix, before writing implementation code
8