payload-cmslisted

# Payload CMS Payload 3.x runs inside a Next.js (or TanStack Start) app: the config is source code, the admin panel is mounted routes, and the database schema is derived from your collections. Prefer the project's existing conventions, then steer with three leading words: **config is the schema**, **access is opt-in**, and **thread the request**. Branch-specific references, loaded on demand: - [reference/collections.md](reference/collections.md) — collection config, auth, uploads, versions and drafts, globals. - [reference/fields.md](reference/fields.md) — field types, virtual and join fields, the experimental `slug` field, validation, type guards. - [reference/access-control.md](reference/access-control.md) — collection, field, and admin access; the Access Operation trap. - [reference/hooks.md](reference/hooks.md) — hook families, argument shapes, `context`, loop prevention. - [reference/queries.md](reference/queries.md) — operators, `depth`, `select`, Local API, transactions. - [reference/mcp.md](reference/mcp.md) — the official `@payloadcms/plugin-mcp` server, its tools and its three authorization gates. - [reference/extending.md](reference/extending.md) — plugin authoring, custom endpoints, jobs queue, storage adapters, localization. ## First Checks 1. Read `payload.config.ts` (repo root or beside `/app`) — `db`, `collections`, `plugins`, `localization` and versions defaults tell you what schema you are editing. 2. Read the installed versions of `