HIGHPerformancesmallNext.js + Supabase Standards

Parallelize independent data fetches with Promise.all

Use Promise.all for independent Supabase queries instead of sequential await chains.

Why This Matters

Sequential awaits create a waterfall — each query waits for the previous one to complete. Three 200ms queries take 600ms sequentially but only 200ms in parallel.

Related Rules

Use route groups to organize app sections

Architecture

HIGH

Colocate page files with their route segment

Architecture

MEDIUM

Use (select auth.uid()) instead of auth.uid() in policies

Performance

MEDIUM

Use kebab-case for file and directory names

Quality

MEDIUM

Catch this automatically on every PR

BeforeMerge scans your pull requests against this rule and 3+ others. Get actionable feedback before code ships.

Join Waitlist Browse All Rules

Why This Matters

Sequential fetches create a waterfall:

Query 1: |████████| 200ms
Query 2:          |████████| 200ms
Query 3:                    |████████| 200ms
Total:                                 600ms

Parallel fetches overlap:

Query 1: |████████| 200ms
Query 2: |████████| 200ms
Query 3: |████████| 200ms
Total:              200ms

Good

const [rules, skills, tags] = await Promise.all([
  getRules(),
  getSkills(),
  getTags(),
])

Bad

const rules = await getRules()   // waits 200ms
const skills = await getSkills() // waits another 200ms
const tags = await getTags()     // waits another 200ms