frappe_agents
CLAUDE.md0 starsChanged 3 months agoMITView on GitHub
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- dev-benchSkill
- releaseSkill
- semantic-commitSkill
- version-branchesSkill
The file
We found no rules to list in this file: it reads as prose or reference rather than instructions.
Files
<!--
A real file, not a symlink to AGENTS.md. Frappe Cloud's marketplace audit blocks
an app that ships a symlink ("symlinks cause build errors"), and this one was the
single blocking finding. The line below is a Claude Code import, so the canonical
rules still live in AGENTS.md and are read from here.
-->@AGENTS.md
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.