nextjs-server-actions
Mutations, Form handling, and RPC-style calls.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Server Actions
Priority: P1 (HIGH)
Handle form submissions and mutations without creating API endpoints.
Implementation
-
Directive: Add
'use server'at the top of an async function. -
Usage: Pass to
actionprop of<form>or invoke from event handlers.
// actions.ts
'use server';
export async function createPost(formData: FormData) {
const title = formData.get('title');
await db.post.create({ title });
revalidatePath('/posts'); // Refresh UI
}
Client Invocation
-
Form:
<form action={createPost}>(Progressive enhancements work without JS). -
Event Handler:
onClick={() => createPost(data)}. -
Pending State: Use
useFormStatushook (must be inside a component rendered within the form).
Validation & Error Handling
-
Zod: Always validate
FormDataor arguments on the server. -
Return Values: Return serializable objects
{ success: boolean, error?: string }to handle feedback on Client.
Security
-
Authentication: Check
auth()(e.g., NextAuth) session inside every Server Action. -
Closure: Be careful with closures in Server Actions defined inside Components (they capture context encrypted). Prefer defining actions in separate files (
actions.ts).
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!