HIGHQualitytrivialNext.js + Supabase Standards

Use revalidatePath after server action mutations

Call revalidatePath() or revalidateTag() after insert/update/delete operations to refresh cached pages.

Why This Matters

Next.js caches aggressively. Without explicit revalidation after mutations, the UI shows stale data until the cache expires.

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

Next.js caches server component renders. After a mutation, the cached version is stale.

Good

"use server"
import { revalidatePath } from "next/cache"
 
export async function updateRule(id: string, data: RuleData) {
  const supabase = createAdminClient()
  await supabase.from("rules").update(data).eq("id", id)
  revalidatePath("/rules")
  revalidatePath(`/rules/${data.slug}`)
}

Bad

export async function updateRule(id: string, data: RuleData) {
  await supabase.from("rules").update(data).eq("id", id)
  // No revalidation — UI shows old data!
}

Use revalidatePath after server action mutations

Why This Matters

Tags

Related Rules

Catch this automatically on every PR

Why This Matters

Good

Bad