pocketbase-best-practiceslisted

# PocketBase Best Practices A curated rule set for PocketBase design decisions, composed over a vendored upstream body of 63 prioritized rules across 9 categories. ## How to use this skill 1. **Start at `base/SKILL.md`** — it carries the full category table and the one-line quick reference for every rule id (`coll-*`, `rules-*`, `auth-*`, `sdk-*`, `query-*`, `realtime-*`, `file-*`, `deploy-*`, `ext-*`). 2. **Load the individual rule** from `base/rules/<rule-id>.md` for the incorrect/correct code pair. Load only the rules the task touches — there are 65 rule files. 3. **Load `base/references/<topic>.md`** for the longer-form treatment of a whole area. 4. **Check "Field notes" below before acting on a rule** — where our verified findings differ from or extend the base, this file wins. ## Scope: design, not operation This skill answers *"is this backend built right"*. It does not drive a running instance. For mode detection, bootstrap, collection/record CRUD, auth calls, backups, migration generation, and Go hooks, use the `pocketbase` skill shipped alongside this one in the same plugin. Rough split: | Question | Skill | |---|---| | Should this be an auth collection or a base collection? | this one | | What API rule expresses "owner or admin"? | this one | | Why is this list endpoint slow? | this one | | Create the collection / run the migration / take a backup | `pocketbase` | | Wire a Go hook or a custom route | `pocketbase` | ## Field notes `references/fi