people-memory-mcp
AGENTS.md1 starsChanged 3 months agoMITView on GitHub
- Use only synthetic people in tests, docs, screenshots, logs, and commits. - Keep all credentials out of Git. Browser code may receive a Supabase publishable key, never a service-role key or PostgreSQL password. - Preserve source and confidence on imported or inferred facts. - Never merge ambiguous identities automatically. - Run uv run ruff check . and uv run pytest after Python changes. - Run supabase db reset after migration changes. - Validate every changed skill and the plugin…
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 repository8 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- enrich-peopleSkill
- import-contactsSkill
- maintain-people-memorySkill
- remember-peopleSkill
- setup-people-memorySkill
- upgrade-people-memorySkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 1 is common, 2 are distinctive, and 2 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- could be automatic: a setting could enforce it
- Distinctive: line 3
Use only synthetic people in tests, docs, screenshots, logs, and commits.
- Common: line 4
Keep all credentials out of Git.
- Distinctive: line 7
Never merge ambiguous identities automatically.
- Very specific: line 8
Run uv run ruff check . and uv run pytest after Python changes.
- Very specific: line 9
Run supabase db reset after migration 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
Repository instructions
- Use only synthetic people in tests, docs, screenshots, logs, and commits.
- Keep all credentials out of Git. Browser code may receive a Supabase publishable key, never a service-role key or PostgreSQL password.
- Preserve source and confidence on imported or inferred facts.
- Never merge ambiguous identities automatically.
- Run
uv run ruff check .anduv run pytestafter Python changes. - Run
supabase db resetafter migration changes. - Validate every changed skill and the plugin manifest before release.
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.