repo-layout
Skill4 starsChanged 27 days agoNo licenceView on GitHub
Decide where a file belongs and keep the repository navigable — the root-directory budget, where superseded documents go, the split between importable modules and runnable recipes, and when dead code is archived rather than left in place. Use when adding a file and the location is not obvious, when naming a package or module, when a document is superseded, when a directory has started mixing live and dead code, and when a newcomer could not tell which files still matter. Also use when the user says "this is disorganized", "where should this go", or "clean up the repo".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- linkpranay-ai/context-engineering-protocoltheir own version, first seen Aug 24, 2026
- fierc3/agent-harness-templatetheir own version, first seen Aug 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- linkpranay-ai/context-engineering-protocol★ 9same name
- fierc3/agent-harness-template★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- block-diagramSkill
- brainstormSkill
- buildSkill
- call-treeSkill
- checkpoint-commitsSkill
- code-proofSkill
- code-tidySkill
- codifySkill
- coding-standardsSkill
- consistencySkill
- escalateSkill
- experimentSkill
- explainSkill
- hparam-priorsSkill
- minimal-coverSkill
- ml_loggingSkill
- notesSkill
- outlineSkill
- plan-docSkill
- prior-workSkill
- project-briefSkill
- proof-of-valueSkill
- recapSkill
- reflectSkill
- reportSkill
- rl-env-mvpSkill
- run-triageSkill
- schema-diagramSkill
- sequence-diagramSkill
- sft-env-mvpSkill
- skill-auditSkill
- skills-repo-accessSkill
- spec-docSkill
- sprint-tasksSkill
- test-planSkill
- tldrSkill
- tune-loopSkill
- tune-preflightSkill
- tune-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
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.