repo-layout
Skill0 starsChanged 3 months agoMITView on GitHub
Use this when finding the right place for code, agent guidance, or temporary task notes in this repository.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- DoKu67/claude-code-skilstheir own version, first seen Oct 16, 2026
- linkpranay-ai/context-engineering-protocoltheir own version, first seen Aug 24, 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
- DoKu67/claude-code-skils★ 4same 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-kickoffSkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 24
Put guidance that applies across the repository in AGENTS.md.
- Very specific: line 26
Put temporary task context in notes/.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Repository layout
This repository separates durable project assets from reusable agent guidance and local working memory.
Locations
AGENTS.mdis the shared, repository-wide contract for coding agents.CLAUDE.mdis the Claude Code entry point and importsAGENTS.md..agents/skills/contains focused skills with owned project knowledge and repeatable workflows. Each skill is in its own directory with aSKILL.md.src/contains durable application source code.notes/is local Markdown scratch space for investigation, planning, decisions, and handoffs during long tasks. Its Markdown files are ignored by Git and should normally remain uncommitted.
Placement rules
Put guidance that applies across the repository in AGENTS.md. Put guidance
for a narrow recurring task in a relevant skill. Put production code in src/.
Put temporary task context in notes/; promote only durable decisions or
documentation to tracked project files when they are ready.
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.

