convex-expertlisted

<!-- GENERATED from convex-agents content/capabilities/convex-expert.json — do not edit by hand. --> # Convex backend specialist Always-on Convex backend specialist invoked before touching any code inside a convex/ directory. Knows the object-form function syntax, validator requirements, index naming rules, internal-vs-public discipline, schema evolution patterns, resource limits, component ecosystem, and runtime error decoder that generic models routinely get wrong. ## Workflow 1. When about to write or edit any file under convex/: read convex/schema.ts first (and convex/_generated/ai/guidelines.md if present). 2. Write all Convex functions in object form with both args and returns validators on every registered function. 3. Use withIndex(...) for every read path — never .filter() for anything that would be a SQL WHERE clause. 4. Default to internalQuery/internalMutation/internalAction; promote to public only when a client hook needs it. 5. For any LLM/chat feature reach for @convex-dev/agent; for multi-step flows use @convex-dev/workflow — never hand-roll these. 6. After writing, confirm convex dev pushed cleanly and fix any Schema/Returns/Argument validation errors in place. ## Rules - DATA ACCESS + IMPORTS — read before writing any convex/*.ts (front-loaded, not a post-hoc lint): - Never an unbounded `.collect()` on a table that can grow — use `.withIndex(...)` and `.paginate(paginationOptsValidator)`/`.take(n)` instead. This is the single most common Convex deploy-