ShipVeryFastShipVeryFast
Documentation

Get help from AI

ShipVeryFast is written to be read by AI editors. The code is strictly typed, conventional Next.js, and the repo ships context files so an agent understands the project before it writes a line.

The context files

  • CLAUDE.md, guidance for Claude Code: stack, architecture, commands, conventions and gotchas.
  • AGENTS.md, the same for Codex and other agents, with concrete API and LLM patterns.
  • .cursorrules, compact rules for Cursor.

Because these live in the repo, any agent you point at the project picks up the same conventions: Zod-validated routes, the NextAuth gate, rate limiting, security logging, and graceful degradation for optional keys.

Get help from AI

The codebase is built to be read by AI editors. Paste this into Claude Code, Cursor or Codex to get context-aware help.

I'm working in the ShipVeryFast Next.js 15 SaaS boilerplate. It ships CLAUDE.md, AGENTS.md and .cursorrules with the project's conventions (Zod-validated API routes, NextAuth gate, rate limiting, security logging, graceful degradation for optional keys). 
Task: <describe what you want to build or change> 
Follow the existing patterns and keep changes typed.

More in Working with AI agents.

Give the agent the page

Stuck on a specific doc? Copy this page's text into your prompt so the agent has the exact context, then ask it to apply the steps to your code.

Build features, not boilerplate

Because every layer is already wired and documented, an agent can generate whole features in minutes: a new dashboard page, an API route with validation, a Stripe-gated section. You review and ship.