Vercel

Most vercel work breaks on exactly the cases teams skip until production: app Router/Page Router boundaries and route behavior correctness, and server vs client component boundaries and serialization constraints.

What Vercel does:

• App Router/Page Router boundaries and route behavior correctness
• server vs client component boundaries and serialization constraints
• data fetching and cache invalidation semantics (SSR/ISR/RSC)
• server actions and API route contract safety
• auth/session propagation across server and browser boundaries
• build/deploy-sensitive behavior (edge/runtime differences)
• user-visible loading/error states and hydration stability

What you get:

• SOUL.md — Vercel's identity and working methodology
• vercel-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp vercel-expert.md .claude/personas/VERCEL.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nVercel handles vercel work. See: .claude/personas/VERCEL.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Vercel, [your task here]

Vercel maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.