builder-skills / templates
AGENTS.md404 starsChanged 45 days agoApache-2.0View on GitHub
[Project name]. [One sentence on what it does and who uses it.] Stack: Convex (backend), [React / Next.js / Vite / Expo] (frontend), [auth provider], [email provider]. For any Convex API, fetch https://docs.convex.dev/llms.txt and follow the link for the area before relying on memory. The skills in .claude/skills/ (or .agents/skills/) cover each area in depth. Load the one that matches the task. Do not run npx convex deploy, git commit, git push, or any publish command unless the current message…
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- waynesutton/convexskillsword for word, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 1
- waynesutton/convexskills★ 405100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- avoid-feature-creepSkill
- convex-agentsSkill
- convex-best-practicesSkill
- convex-component-authoringSkill
- convex-cron-jobsSkill
- convex-file-storageSkill
- convex-functionsSkill
- convex-http-actionsSkill
- convex-migrationsSkill
- convex-realtimeSkill
- convex-schema-validatorSkill
- convex-security-auditSkill
- convex-security-checkSkill
- convexSkill
- git-safetySkill
- project-docsSkill
- project-workflowSkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Do not run npx convex deploy, git commit, git push, or any publish command unless the current message asks for it.
- Very specific: line 44
Every function uses the object form with args and returns validators.
- Very specific: line 51
Keep query / mutation / action wrappers thin.
- Very specific: line 56
After a change lands, sync task.md, changelog.md, files.md.
- Very specific: line 57
Before any git command that could discard work, load the git-safety skill.
- Distinctive: line 62
No emojis. No em dashes.
- Distinctive: line 64
No placeholder text or images.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project context
[Project name]. [One sentence on what it does and who uses it.]
Stack: Convex (backend), [React / Next.js / Vite / Expo] (frontend), [auth provider], [email provider].
Docs first
For any Convex API, fetch https://docs.convex.dev/llms.txt and follow the link for the area before relying on memory. The skills in .claude/skills/ (or .agents/skills/) cover each area in depth. Load the one that matches the task.
Commands
npx convex dev # development. watches, syncs, regenerates types
npx convex dev --once # single sync
npx convex run file:fn '{}' # run a function with args
npx convex logs # tail logs
npx convex dashboard # open dashboard
npm run typecheck # tsc --noEmit
npm run lint # eslint with @convex-dev/eslint-pluginDo not run npx convex deploy, git commit, git push, or any publish command unless the current message asks for it.
Layout
convex/
_generated/ generated, never edit, commit to git
schema.ts tables, validators, indexes
http.ts http router (exact name required)
crons.ts cron jobs
convex.config.ts components registered with app.use
<feature>.ts functions, referenced as api.<feature>.<name>
src/ frontend
prds/ one PRD per non trivial change, plus lessons.md
files.md what each file is for
changelog.md Keep a Changelog, dates from git log
task.md To Do / In Progress / CompletedRules that hold everywhere
- Every function uses the object form with
argsandreturnsvalidators.returns: v.null()when nothing comes back. withIndexoverfilter. Index names list their fields:by_user_and_status.- Mutations are idempotent. Early return when the doc is already in the target state. Patch without reading first when possible.
- Schedule
internal.*functions only. Neverapi.*. - No
Date.now()inside a query. Pass time as an argument. "use node"only in action files that need Node APIs. No queries or mutations in those files.- Throw
ConvexErrorfor errors the client should see. - Keep
query/mutation/actionwrappers thin. Logic lives in plain functions.
Workflow
- Non trivial work starts with a PRD in
prds/. Load theproject-workflowskill. - After a change lands, sync
task.md,changelog.md,files.md. Load theproject-docsskill. - Before any git command that could discard work, load the
git-safetyskill. - The request sets the scope. Extra ideas go in the summary, not the diff. Load
avoid-feature-creepif unsure.
Style
- No emojis. No em dashes.
- Site design system for modals, alerts, confirmations. Never
window.confirmoralert. - No placeholder text or images. Everything renders real data from Convex.
- Short comments that say what a block is for.
- Type safe. No
any.
Project notes
[Business rules, naming conventions, architecture decisions, things that bit you before.]
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

