production-saas-starter / go-b2b-starter
AGENTS.md532 starsChanged 49 days agoMITView on GitHub
Read the shared rules in ../AGENTS.md, ../README.md and ../docs/ARCHITECTURE.md. This project owns business endpoints, tenant authorization, SQLC, forward migrations and the business API contract. Use .agents/skills/go-backend/SKILL.md and .agents/agents/backend-builder.md inside this directory. Go tests, database checks and SQLC generation belong here. Follow the skill's repository-relative commands; from this directory, make test, make vet and make sqlc-check are the corresponding local targets. Database tests require a disposable database. Identity, sessions and organization membership belong to Better Auth in Next.js. For that boundary,…
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,542 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- next_b2b_starter/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- go-b2b-starter/CLAUDE.mdCLAUDE.md
- next_b2b_starter/CLAUDE.mdCLAUDE.md
- dev-toolsSkill
- orchestrationSkill
- pr-reviewSkill
- service-connectionsSkill
- dev-toolsSkill
- orchestrationSkill
- pr-reviewSkill
- service-connectionsSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Read the shared rules in ../AGENTS.md, ../README.md and ../docs/ARCHITECTURE.md.
- Very specific: line 20
Run node ../scripts/harness.mjs check for tooling changes.
≈ “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
Go project
Read the shared rules in ../AGENTS.md, ../README.md and
../docs/ARCHITECTURE.md. This project owns business endpoints, tenant
authorization, SQLC, forward migrations and the business API contract.
Use .agents/skills/go-backend/SKILL.md and
.agents/agents/backend-builder.md inside this directory. Go tests, database
checks and SQLC generation belong here. Follow the skill's repository-relative
commands; from this directory, make test, make vet and make sqlc-check
are the corresponding local targets. Database tests require a disposable database.
Identity, sessions and organization membership belong to Better Auth in Next.js.
For that boundary, consult
../next_b2b_starter/.agents/skills/auth-integration/SKILL.md; hand changes to
its owner rather than duplicating the auth policy here. Hand the tested Go-owned
API schema and permission/error contract to the frontend owner before parallel UI
work. Never hand-edit SQLC or TypeScript generated output.
Run node ../scripts/harness.mjs check for tooling changes. Canonical Go guidance
lives here; generated .claude/ and .codex/ files are adapters. Root guidance
coordinates shared work and does not replace these project instructions.
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.