server-actions Cursor ruleA

server-actions from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.

Install it, pinned
mdr add vibestackdev/vibe-stack/.cursor/rules/server-actions.mdc@git:20260401.7160e4c

Pins git:20260401.7160e4c in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
Cursor rule
Repository
vibestackdev/vibe-stack
Path
.cursor/rules/server-actions.mdc
Versions recorded
2
Latest version
git:20260401.7160e4c, committed Apr 1, 2026
First version recorded
Mar 30, 2026
Size
3,329 bytes
Repository stars
8
License
MIT

Guidelines for Server Actions — validation, error handling, and when to use Route Handlers instead.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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.

```typescript
'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()
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add vibestackdev/vibe-stack/.cursor/rules/server-actions.mdc@sha256:6a89b37ecf380dcb

The line at the top of this page pins the label git:20260401.7160e4c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_jhhamqq5jqdr5xlm.svg)](https://markdownregistry.com/a/art_jhhamqq5jqdr5xlm)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in vibestackdev/vibe-stack/.cursor/rules/server-actions.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of server-actions.mdc from somewhere else? Ask it: where did my server-actions.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Mar 30, 2026 and Apr 1, 2026, about one every 2 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260401.7160e4c latest2026-04-01 7160e4c 3,329 BA view · diff
git:20260330.dd1a8a92026-03-30 dd1a8a9 2,220 BA view
Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (3329 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

vibestackdev/vibe-stack · 8 stars · license MIT · pushed 2026-11-17 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_jhhamqq5jqdr5xlm
GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/server-actions.mdc
GET https://markdownregistry.com/api/v1/blob/6a89b37ecf380dcb36f494aaac4fc53fa1c2e3592f967798791401007739af40

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: Cursor rules vs AGENTS.md · which agent file does what.

More from vibestackdev/vibe-stack

ai-collaboration Cursor rule
vibestackdev/vibe-stack · .cursor/rules/ai-collaboration.mdc · Instructions for AI agent code generation workflow
git:20260401.56e571e · audit A · 8 stars
api-design Cursor rule
vibestackdev/vibe-stack · .cursor/rules/api-design.mdc · API route handler design patterns
git:20260330.dd1a8a9 · audit A · 8 stars
api-validation Cursor rule
vibestackdev/vibe-stack · .cursor/rules/api-validation.mdc · API route validation — enforces Zod validation on all route handlers and server actions
git:20260401.d240055 · audit A · 8 stars
caching-revalidation Cursor rule
vibestackdev/vibe-stack · .cursor/rules/caching-revalidation.mdc · Next.js caching and revalidation best practices
git:20260330.dc27980 · audit A · 8 stars
context-management Cursor rule
vibestackdev/vibe-stack · .cursor/rules/context-management.mdc · Context window management — prevents AI from losing track during long sessions
git:20260401.56e571e · audit A · 8 stars
database-design Cursor rule
vibestackdev/vibe-stack · .cursor/rules/database-design.mdc · Database schema design patterns for Supabase with proper types and relationships
git:20260330.1081646 · audit A · 8 stars
env-management Cursor rule
vibestackdev/vibe-stack · .cursor/rules/env-management.mdc · Environment variable management and secrets handling
git:20260330.1081646 · audit A · 8 stars
error-handling Cursor rule
vibestackdev/vibe-stack · .cursor/rules/error-handling.mdc · Error boundaries, loading states, and server error handling
git:20260401.56e571e · audit A · 8 stars
file-naming Cursor rule
vibestackdev/vibe-stack · .cursor/rules/file-naming.mdc · File naming conventions and project organization rules
git:20260330.1081646 · audit A · 8 stars
file-uploads Cursor rule
vibestackdev/vibe-stack · .cursor/rules/file-uploads.mdc · Image and file upload patterns — prevents insecure client-side uploads and missing file validation
git:20260401.d240055 · audit A · 8 stars
git-conventions Cursor rule
vibestackdev/vibe-stack · .cursor/rules/git-conventions.mdc · Git workflow and commit conventions for AI-assisted development
git:20260330.dd1a8a9 · audit A · 8 stars
hydration-safety Cursor rule
vibestackdev/vibe-stack · .cursor/rules/hydration-safety.mdc · React hydration mismatch prevention
git:20260330.dc27980 · audit A · 8 stars

Every file in vibestackdev/vibe-stack

Browse by kind, by grade A, or by owner.