Next.js Server Actions & Routes Standards FAQs

Question 1

What is the recommended file structure for actions?

Accepted Answer

Actions should be gathered in the `src/server/actions/` directory and use the naming convention `[feature].actions.ts` with a file-level 'use server' directive.

Question 2

When should I use Server Actions instead of Route Handlers?

Accepted Answer

Server Actions are the primary choice for CRUD operations, form submissions, and state changes. Route Handlers should be reserved for SSE, Webhooks, Cron jobs, or when specific HTTP methods/headers are required.

Question 3

How does this skill improve Next.js security?

Accepted Answer

It enforces mandatory authentication checks at the start of every action, restricts destructive operations when 'view mode' is enabled, and prevents direct database access from unprotected client-side code.

Question 4

Does this skill require Zod for validation?

Accepted Answer

Yes, it mandates the use of Zod schemas to parse or safe-parse all input arguments in Server Actions to guarantee type safety and prevent malicious data injection.

Question 5

Can this skill help prevent common Next.js anti-patterns?

Accepted Answer

Absolutely. It specifically flags errors like putting 'use server' inside Route Handlers or performing unauthorized DB operations using service roles.

Next.js Server Actions & Routes Standards

About

Key Features

Use Cases

Next.js Server Actions & Routes Standards

About

Key Features

Use Cases