MEDIUMQualitysmallNext.js + Supabase Standards

Return structured results from server actions

Return { success: true, data } or { success: false, error } instead of throwing errors from server actions.

Why This Matters

Thrown errors from server actions surface as generic "something went wrong" in the UI. Structured results enable specific error messages.

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

Structured results are:

Predictable — caller always gets the same shape
Debuggable — error messages are specific
Type-safe — TypeScript can narrow the result

Good

export async function createRule(data: RuleInput) {
  try {
    const { orgId } = await requireAuth()
    const result = await admin.from("rules").insert({ ...data, organization_id: orgId })
    return { success: true, data: result.data }
  } catch (error) {
    return { success: false, error: "Failed to create rule" }
  }
}

Return structured results from server actions

Why This Matters

Tags

Related Rules

Catch this automatically on every PR

Why This Matters

Good