Standardize Next.js 16+ server actions and route handlers with Zod validation and ActionResult contracts.
npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-api
Please help me install this Agent Skill. Skill: kb-api Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/kb-api Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-api
It prevents inconsistent API behavior in Next.js 16+ by standardizing how server actions and route handlers handle validation, authorization, revalidation, and error responses.
getEntities, getEntityById, createEntity, updateEntity, and deleteEntity semantics that work across projects.safeParse exactly once at the action or route boundary to establish a clear trust boundary.revalidatePath only after a real mutation succeeds, and never on read-only actions.params and searchParams as Promises and parses them safely with await.Implement your server action or route handler using the ActionResult<T> pattern, validate inputs with Zod safeParse at the boundary, and call revalidatePath only on the success path after the mutation completes.
High-intent search queries and answers about installing and using this skill.
Use an ActionResult<T> discriminated-union contract to reliably separate success data from user-facing error strings in Next.js server actions, ensuring cleaner consumer branching for consistent error handling.
Apply revalidatePath only after a real mutation succeeds in your Next.js server action, and never on read-only actions, to ensure success-only cache invalidation and prevent stale data.
Choose Next.js server actions or route handlers based on your mutation semantics and HTTP status/body conventions; server actions standardize validation via Zod safeParse, while route handlers require explicit HTTP status codes.
Enforce Zod safeParse exactly once at the action or route boundary in Next.js to establish a clear trust boundary, validating inputs before processing mutations or returning ActionResult<T> responses.
Yes, Next.js 16+ treats params and searchParams as Promises, requiring you to safely await and parse them before use in server actions and route handlers to avoid runtime errors.
Define portable CRUD action signatures like getEntities, getEntityById, createEntity, updateEntity, and deleteEntity in Next.js to maintain consistent semantics and validation across projects.
Ikram-AlamBuild Next.js 16 applications with updated patterns for pages, layouts, and API routes.
sgcarstrendsCreate or update Next.js server actions with Zod validation and cache revalidation.
omicverseConverts bulk RNA-seq FASTQ or SRA inputs into gene-level count matrices.
naporin0624Create type-safe IPC routes with Hono and Zod validation.