Error boundary hierarchy, structured logging with pino, user-friendly error messages, and Supabase error code reference.
Checklist
Auto-generated from the 6 rules this article references — each links to the enforceable rule.
References
Addresses
Rules
Call auth.getUser() immediately after creating the server client in middlewareUse error.tsx for route-level error boundariesUse requireAuth() as the first call in every authenticated server actionUse server components for data fetching by defaultValidate all server action inputs at the boundaryUse (select auth.uid()) instead of auth.uid() in policies
Tags
nextjssupabase
More from this skill
Explore more rules and knowledge
BeforeMerge offers hundreds of code review rules, guides, and detection patterns to help your team ship better code.