onequery
AGENTS.md17 starsChanged 6 months agoApache-2.0View on GitHub
If you encounter something surprising or confusing in this project, flag it as a comment.
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,700 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.
- agent-browserSkill
- agentic-legibilitySkill
- babysit-prSkill
- better-result-adoptSkill
- code-breaking-changesSkill
- code-review-change-sizeSkill
- code-reviewSkill
- code-review-testingSkill
- drizzle-migration-conflict-resolutionSkill
- gh-pr-writingSkill
- knip-deadcodeSkill
- onequery-blog-imagesSkill
- onequery-bugSkill
- onequery-pr-bodySkill
- protobufSkill
- react-no-use-effectSkill
- tanstack-query-best-practicesSkill
- tanstack-router-best-practicesSkill
- xstateSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 1
If you encounter something surprising or confusing in this project, flag it as a comment.
≈ “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
If you encounter something surprising or confusing in this project, flag it as a comment.
- Runtime: Node.js mostly, (Rust for
apps/cli). - Contract: Connect RPC (Protobuf contracts locates at
proto/) - Testing: Vitest
- Linter/formatter: oxlint, oxfmt
- For linting, use
bun lint --format json. For type-aware lint, append--type-awareflag (takes more time then normal lint). - For checking lint/format for whole monorepo, use
bunx turbo check --json, to fix,bunx turbo check:fix - For type checking, use
bunx turbo typecheck --json. - For testing, use
bunx turbo test --json, notbun test. - For tools, use
mise exec.
Auto-generated files and how to generate them:
NOTE: Don't edit them manually.
packages/proto-cli/src/**- Generated by Buf fromonequery/cli/v1packages/proto-runtime/src/**- Generated by Buf fromonequery/runtime/v1packages/proto-workflow/src/**- Generated by Buf fromonequery/workflow/v1packages/cli-server/src/connect/**contains handwritten Connect handlers/adapters that import generated service descriptors frompackages/proto-*.
apps/dashboard/src/routeTree.gen.ts- Generated by TanStack Router**/worker-configuration.d.ts- Generated by Wranglerpackages/ui/src/components/ui/**- Generated by shadcn/ui CLIpackages/db/src/migrations/**- Generated by Drizzle CLI
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.