Imported from rebasepro/rebase (AGENTS.md). Install upstream with npx skills add rebasepro/rebase. Copyright stays with the author.

Working in this repository

Rules for coding agents working on the Rebase monorepo. They apply to humans too. The detailed guides live in .agent/workflows/. Read the one that matches the task before you start:

• coding-standards.md covers the TypeScript rules (no any, no structural casts, isSQLAdmin), i18n, and the auth helpers.
• rebase-architecture.md covers package entry points, CMS vs. Studio mode, and where code belongs.
• schema-migration.md covers changing a collection and applying the migration, including every relation kind.
• ui-components.md covers the @rebasepro/ui kit and the design reference. Read it before building any UI.
• deployment.md covers deploys and releases: never do either without an explicit request.

Always

• Use pnpm only. Never npm or yarn.
• The UI must stay coherent. Build from the @rebasepro/ui kit, not raw HTML or ad-hoc classes. UIReferenceView (packages/app/src/debug/UIReferenceView.tsx, at /debug/ui in the example app) is the design source of truth. Read it, or ContentHomePage / StudioHomePage, before creating a view.
• Author collections with defineCollection from @rebasepro/cms-types. Presentation options live under admin (admin.display.title, admin.propertiesOrder, …). A relation is a property of type: "relation" whose relation.kind is one of belongsTo, hasOne, hasMany, manyToMany or via. Read packages/types/src/types/relations.ts before writing anything unusual.
• Never convert to any, and never cast structurally around a type (for example driver as { executeSql?: … }). To run raw SQL, narrow driver.admin with isSQLAdmin from @rebasepro/types.
• Put scripts in tooling/scripts/. Never put one-off scripts, codemods, logs or diffs in the repo root or inside a package. For truly throwaway files, use your own scratch directory outside the repository.
• Ask before touching the local environment. Present a plan and get approval before changing database settings, .env files, or creating or dropping databases and roles.
• Never release without consent. Never publish, tag or release a package unless the user asked for that exact release, in the moment. Deploys are gated the same way. See deployment.md for what counts and what to do instead.
• Verify before you say it is done. ./tooling/scripts/verify-quality.sh runs what CI runs: the static gates, the unit tests, the build gates and the Playwright suite. For a docs-only change, pnpm verify:docs:strict is the gate that reads it.

Measuring agent changes

pnpm harness:eval -- --list shows benchmark tasks derived from real fix commits in this repo. Use them to check whether a change to agent instructions or tooling helps or regresses. See tooling/scripts/harness/README.md.