Enforce BFF standards for Next.js Server Actions and Route Handlers.
npx skills add https://github.com/dtaborda/startup-saas-template --skill template-bff
Please help me install this Agent Skill. Skill: template-bff Source: https://github.com/dtaborda/startup-saas-template/tree/main/skills/template-bff Command: npx skills add https://github.com/dtaborda/startup-saas-template --skill template-bff
Template-bff codifies backend-for-frontend Server Action and Route Handler practices so the ui/ layer never bypasses Supabase abstractions, validation contracts, or standardized action results, eliminating scattered business logic and inconsistent data flows.
@template/contracts, delegation of business logic to @template/core, and returning ActionResult<T> so components can react predictably.Request template-bff to implement a Server Action that validates input with @template/contracts, delegates to @template/core, and returns an ActionResult so UI components can handle success or failure predictably.
High-intent search queries and answers about installing and using this skill.
Next.js Server Actions should enforce Zod validation through contracts, delegate business logic to core modules, and return standardized ActionResult objects so UI components react predictably to data mutations and streaming responses.
Use Next.js Route Handlers instead of Server Actions when handling webhook orchestration or Server-Sent Events (SSE), as route handlers provide proper header control, streaming flow management, and centralized error handling for API logic.
The best way to validate Supabase data fetching in Next.js App Router is applying Zod schemas via shared contracts and accessing Supabase exclusively through core abstractions to prevent scattered business logic and bypassed data flows.
No, direct Supabase imports inside Next.js Server Actions are prohibited; you must access Supabase exclusively through designated core modules to ensure consistent backend-for-frontend abstractions and standardized data flows.
Zod validation works with Next.js Route Handlers and Server Actions by requiring schemas defined within shared contracts rather than inline, ensuring all server-side input is validated before business logic execution.
Next.js Server Actions return inconsistent data formats to the client when bypassing standardized ActionResult responses; enforcing typed ActionResult objects ensures components handle success and failure predictably.
AlteriomEstablish end-to-end type-safe APIs in TypeScript apps using tRPC, Zod, and Next.js.
davepoonImplement Next.js App Router API route handlers with HTTP methods and streaming.
dtabordaEnforce @template/contracts imports and shared Zod schemas across code reviews.
mcclowesGuide Next.js App Router patterns for route handlers, server actions, and streaming.