server-actions

Guidance for choosing between Next.js Server Actions and Route Handlers, with rules for validation and consistent action responses.

In plain words
What is it for?
Use it for form submissions, database changes, webhooks, public APIs, file transfers, OAuth callbacks, and other server-side operations.
Why use it?
It helps keep form mutations and API endpoints in the right place while avoiding leaked errors and unvalidated input.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/vibestackdev/vibe-stack/server-actions
Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 834 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00834
Opus 5 $0.00000 $0.00417
Sonnet 5 $0.00000 $0.00167
Haiku 4.5 $0.00000 $0.00083

Measured yesterday against content hash 6a89b37ecf38, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

server-actions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/server-actions.mdc · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Server Actions vs Route Handlers

When to Use Server Actions

  • Form submissions (POST with user data)
  • Mutations triggered from UI (create, update, delete)
  • Operations needing cookie/session access
  • Revalidation of cached pages after a mutation

When to Use Route Handlers (app/api/**)

  • Webhooks (Stripe, GitHub — external services calling your API)
  • Public API endpoints (no auth needed or API key auth)
  • File upload/download streams
  • Third-party OAuth callbacks
  • CORS-required endpoints

RULE 1: Always Use Typed ActionResponse

Every Server Action MUST return ActionResponse<T> — never throw, never leak internals.

'use server'
import { z } from 'zod'
import { createClient } from '@/lib/supabase/server'
import { revalidatePath } from 'next/cache'

type ActionResponse<T = void> =
  | { success: true; data: T }
  | { success: false; error: string }

const CreateTodoSchema = z.object({
  title: z.string().min(1, 'Title required').max(200),
})

export async function createTodo(
  formData: FormData
): Promise<ActionResponse<{ id: string }>> {
  // 1. Auth first
  const supabase = await createClient()
  const { data: { user } } = await supabase.auth.getUser()
  if (!user) return { success: false, error: 'Unauthorized' }

  // 2. Validate
  const parsed = CreateTodoSchema.safeParse({ title: formData.get('title') })
  if (!parsed.success) {
    return { success: false, error: parsed.error.issues[0].message }
  }

  // 3. Execute
  const { data, error } = await supabase
    .from('todos')
    .insert({ title: parsed.data.title, user_id: user.id })
    .select('id')
    .single()

  if (error) {
    console.error('[CREATE_TODO_ERROR]', error) // Server-side only
    return { success: false, error: 'Failed to create todo' } // Generic to client
  }

  revalidatePath('/todos')
  return { success: true, data: { id: data.id } }
}

RULE 2: Never Export Non-Action Values from 'use server' Files

Files with 'use server' export ONLY async functions. Never export constants, types, or synchronous functions from these files.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 113 lines · 0 tokens per session scan A 6a89b37ecf38

Subscribe to this mod's changes

server-actions is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 834 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.