Critical rules: a server function is an independent HTTP endpoint reachable directly, so a route's beforeLoad redirect protects the UI only — auth must live inside the handler or its middleware for every function touching private data; never use Next.js/Remix patterns ("use server", getServerSideProps, Remix loader/action); loaders are isomorphic, so DB/secrets/filesystem access belongs in a server function, never a loader; useServerFn is mandatory when a function throws redirect() or notFound() (optional otherwise); and strict serialization is on by default (FormData allowed as POST input, Response as output).
Includes templates for a full CRUD module and for FormData submissions with Zod validation.
Do NOT use this skill for raw external/public HTTP endpoints (use start-server-routes), for composable middleware chains (use start-middleware), or for Next.js/Remix "use server" patterns.
TanStack Start Server Functions
Server functions are same-origin, type-safe RPC endpoints created with
createServerFn. They run only on the server but are callable from loaders,
components, hooks, and other server functions. This skill targets
@tanstack/react-start v1.166.2.
Agent Workflow (MANDATORY)
Before implementing, verify current APIs against Context7
(/websites/tanstack_start_framework_react) + Exa, then explore the target
codebase. After changes, run fuse-ai-pilot:sniper.
Critical Rules (read first)
- A server function is an independent HTTP endpoint. A route
beforeLoad
redirect protects the route UI, NOT the RPC — an attacker can hit the
endpoint directly. Put auth inside the .handler() or in middleware for
every function touching private data.
- Never use Next.js/Remix patterns. No
"use server", getServerSideProps,
Remix loader/action, or react-router-dom. Use createServerFn
exclusively (from @tanstack/react-start).
- Loaders are isomorphic (run on client AND server). DB queries, secrets,
and file-system access MUST live in a server function, never in a loader.
useServerFn is MANDATORY when the function does throw redirect() or
throw notFound() — the hook wires the throw into the router. Optional for
plain-data functions (a direct call or useMutation/useQuery is fine).
- Strict serialization is on by default. Validator input and handler return
types must be serializable (
FormData allowed as POST input, Response
allowed as output). strict: false disables only the TS check, not runtime.
Overview
| When to Use |
Do NOT Use |
| Internal type-safe RPC from your own app |
Public/cross-origin API (use start-server-routes) |
| Data fetching in loaders |
Raw HTTP method routing on a URL path |
| Mutations from event handlers |
Composable auth/logging chains (use start-middleware) |
Architecture
src/utils/
├── users.functions.ts # createServerFn wrappers — safe to import anywhere
├── users.server.ts # Server-only helpers (DB queries, secrets)
└── schemas.ts # Shared Zod schemas — client-safe
The build replaces server function bodies with RPC stubs in the client bundle,
so static imports of .functions.ts from client components are safe.
→ See crud-server-functions.md
Reference Guide
Concepts
| Topic |
Reference |
Load when |
| Creating functions |
creating.md |
Defining createServerFn, validators, serialization |
| Calling functions |
calling.md |
Invoking from loaders/components, useServerFn, redirect/notFound |
| Security |
security.md |
Enforcing auth, CSRF, caching auth'd responses |
Templates
| Template |
When to Use |
| crud-server-functions.md |
Building a full CRUD module |
| form-with-validation.md |
Handling FormData submissions with Zod |
Quick Reference
Basic function with validation
import { createServerFn } from '@tanstack/react-start'
import { z } from 'zod'
export const createUser = createServerFn({ method: 'POST' })
.validator(z.object({ name: z.string().min(1) }))
.handler(async ({ data }) => db.users.create(data))
await createUser({ data: { name: 'John' } })
Redirect (requires useServerFn in components)
import { useServerFn } from '@tanstack/react-start'
import { redirect } from '@tanstack/react-router'
const signup = createServerFn({ method: 'POST' })
.handler(async () => { throw redirect({ to: '/dashboard' }) })
// In a component:
const signupFn = useServerFn(signup)
→ See calling.md for the full redirect/notFound rules
Best Practices
DO
- Enforce auth inside every handler that reads/writes private data
- Split server-only helpers into
.server.ts, wrappers into .functions.ts
- Validate every input crossing the network boundary with Zod
- Wrap with
useServerFn when in doubt (no-op for plain-data functions)
DON'T
- Rely on route guards to protect a server function
- Use
"use server", getServerSideProps, or Remix action
- Put DB queries or secrets in a route loader
- Dynamically
import() server functions (breaks bundler shaking)
1---2name: start-server-functions3description: Use when creating type-safe RPC server logic with createServerFn — validators, handlers, FormData, redirects. Do NOT use for raw HTTP endpoints or middleware chains.4version: 1.0.05user-invocable: true6references: references/creating.md, references/calling.md, references/security.md, references/templates/crud-server-functions.md, references/templates/form-with-validation.md7metadata:8 source: https://skillmd.com/skills/fusengine/start-server-functions9---1011<objective>12Covers createServerFn, TanStack Start's same-origin type-safe RPC mechanism: GET/POST methods, .validator() (Zod or a plain function), .handler(), the useServerFn hook, FormData input, Response output, strict serialization, throwing redirect()/notFound(), server context utilities, and CSRF protection. Server functions run only on the server but are callable from loaders, components, hooks, and other server functions. Targets @tanstack/react-start v1.166.2.1314Critical rules: a server function is an independent HTTP endpoint reachable directly, so a route's beforeLoad redirect protects the UI only — auth must live inside the handler or its middleware for every function touching private data; never use Next.js/Remix patterns ("use server", getServerSideProps, Remix loader/action); loaders are isomorphic, so DB/secrets/filesystem access belongs in a server function, never a loader; useServerFn is mandatory when a function throws redirect() or notFound() (optional otherwise); and strict serialization is on by default (FormData allowed as POST input, Response as output).1516Includes templates for a full CRUD module and for FormData submissions with Zod validation.1718Do NOT use this skill for raw external/public HTTP endpoints (use start-server-routes), for composable middleware chains (use start-middleware), or for Next.js/Remix "use server" patterns.19</objective>2021# TanStack Start Server Functions2223Server functions are same-origin, type-safe RPC endpoints created with24`createServerFn`. They run only on the server but are callable from loaders,25components, hooks, and other server functions. This skill targets26`@tanstack/react-start` **v1.166.2**.2728## Agent Workflow (MANDATORY)2930Before implementing, verify current APIs against Context731(`/websites/tanstack_start_framework_react`) + Exa, then explore the target32codebase. After changes, run `fuse-ai-pilot:sniper`.3334## Critical Rules (read first)35361. **A server function is an independent HTTP endpoint.** A route `beforeLoad`37 redirect protects the route UI, NOT the RPC — an attacker can hit the38 endpoint directly. Put auth **inside** the `.handler()` or in middleware for39 every function touching private data.402. **Never use Next.js/Remix patterns.** No `"use server"`, `getServerSideProps`,41 Remix `loader`/`action`, or `react-router-dom`. Use `createServerFn`42 exclusively (from `@tanstack/react-start`).433. **Loaders are isomorphic** (run on client AND server). DB queries, secrets,44 and file-system access MUST live in a server function, never in a loader.454. **`useServerFn` is MANDATORY** when the function does `throw redirect()` or46 `throw notFound()` — the hook wires the throw into the router. Optional for47 plain-data functions (a direct call or `useMutation`/`useQuery` is fine).485. **Strict serialization is on by default.** Validator input and handler return49 types must be serializable (`FormData` allowed as POST input, `Response`50 allowed as output). `strict: false` disables only the TS check, not runtime.5152## Overview5354| When to Use | Do NOT Use |55|-------------|------------|56| Internal type-safe RPC from your own app | Public/cross-origin API (use start-server-routes) |57| Data fetching in loaders | Raw HTTP method routing on a URL path |58| Mutations from event handlers | Composable auth/logging chains (use start-middleware) |5960## Architecture6162```63src/utils/64├── users.functions.ts # createServerFn wrappers — safe to import anywhere65├── users.server.ts # Server-only helpers (DB queries, secrets)66└── schemas.ts # Shared Zod schemas — client-safe67```6869The build replaces server function bodies with RPC stubs in the client bundle,70so static imports of `.functions.ts` from client components are safe.7172→ See [crud-server-functions.md](references/templates/crud-server-functions.md)7374## Reference Guide7576### Concepts7778| Topic | Reference | Load when |79|-------|-----------|-----------|80| Creating functions | [creating.md](references/creating.md) | Defining createServerFn, validators, serialization |81| Calling functions | [calling.md](references/calling.md) | Invoking from loaders/components, useServerFn, redirect/notFound |82| Security | [security.md](references/security.md) | Enforcing auth, CSRF, caching auth'd responses |8384### Templates8586| Template | When to Use |87|----------|-------------|88| [crud-server-functions.md](references/templates/crud-server-functions.md) | Building a full CRUD module |89| [form-with-validation.md](references/templates/form-with-validation.md) | Handling FormData submissions with Zod |9091## Quick Reference9293### Basic function with validation9495```tsx96import { createServerFn } from '@tanstack/react-start'97import { z } from 'zod'9899export const createUser = createServerFn({ method: 'POST' })100 .validator(z.object({ name: z.string().min(1) }))101 .handler(async ({ data }) => db.users.create(data))102103await createUser({ data: { name: 'John' } })104```105106### Redirect (requires useServerFn in components)107108```tsx109import { useServerFn } from '@tanstack/react-start'110import { redirect } from '@tanstack/react-router'111112const signup = createServerFn({ method: 'POST' })113 .handler(async () => { throw redirect({ to: '/dashboard' }) })114115// In a component:116const signupFn = useServerFn(signup)117```118119→ See [calling.md](references/calling.md) for the full redirect/notFound rules120121## Best Practices122123### DO124- Enforce auth inside every handler that reads/writes private data125- Split server-only helpers into `.server.ts`, wrappers into `.functions.ts`126- Validate every input crossing the network boundary with Zod127- Wrap with `useServerFn` when in doubt (no-op for plain-data functions)128129### DON'T130- Rely on route guards to protect a server function131- Use `"use server"`, `getServerSideProps`, or Remix `action`132- Put DB queries or secrets in a route loader133- Dynamically `import()` server functions (breaks bundler shaking)