hotrod
CLAUDE.md1 starsChanged 12 days agoMITView on GitHub
- Everything above comes from AGENTS.md, imported verbatim. Edit the rules there, not here, so every agent sees the same rules. - Skills in .claude/skills/ load by their description. When you add or rename one, update the skills table in AGENTS.md in the same change.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- compose-blockSkill
- compose-pageSkill
- write-a-skillSkill
The file
Files
CLAUDE.md — Hotrod
@AGENTS.md
Claude Code specifics
- Everything above comes from
AGENTS.md, imported verbatim. Edit the rules there, not here, so every agent sees the same rules. - Skills in
.claude/skills/load by theirdescription. When you add or rename one, update the skills table inAGENTS.mdin the same change.
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.