agent-config
AGENTS.md8 starsChanged 3 months agoMITView on GitHub
These instructions apply only when working in this repository. This checkout is the live source behind the Claude configuration and the shared instruction and skill links. Preserve that symlink-based layout, leave ignored runtime and session state alone, and keep shared instructions and skills portable across Claude, Codex, and Grok.
In this repository15 other files it gives its agents.
- instructions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- exploreSkill
- featureSkill
- find-sessionSkill
- fix-ciSkill
- humanizerSkill
- kauffj-voiceSkill
- proposeSkill
- review-prSkill
- review-securitySkill
- review-simplicitySkill
- review-uiSkill
- workspaceSkill
- writingSkill
The file
Files
Repository-specific guidance
These instructions apply only when working in this repository.
This checkout is the live source behind the Claude configuration and the shared instruction and skill links. Preserve that symlink-based layout, leave ignored runtime and session state alone, and keep shared instructions and skills portable across Claude, Codex, and Grok.
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.