project-map
Skill19 starsChanged 37 days agoMITView on GitHub
Generate or refresh the project map artifact. Use after significant repository structure changes or when the map is missing or stale.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- mmungdong/skillstheir own version, first seen Nov 1, 2026
- Isabella-a/Skillstheir own version, first seen Oct 19, 2026
- ShlomiPorush/agent-skillstheir own version, first seen Oct 13, 2026
- Tyr9102/project-maptheir own version, first seen Oct 11, 2026
- DanielGodriNeto/claude-skillstheir own version, first seen Oct 5, 2026
- yeaboi-ai/yeaboi.aitheir own version, first seen Sep 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Tyr9102/project-map★ 8same name
- yeaboi-ai/yeaboi.ai★ 4same name
- Isabella-a/Skills★ 2same name
- ShlomiPorush/agent-skills★ 2same name
- DanielGodriNeto/claude-skills★ 1same name
- mmungdong/skills★ 1same name
- TheophilusChinomona/idev★ 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- broSkill
- closingSkill
- context-auditSkill
- decision-logSkill
- dependency-freshnessSkill
- documentation-updateSkill
- failure-learningSkill
- git-disciplineSkill
- goblin-modeSkill
- run-and-verifySkill
- spec-from-screenshotSkill
- ui-qaSkill
- sdd-updateSkill
- sdd-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Create or update the project map — the concise orientation artifact (default <harness-dir>/context/project-map.md) that tells the agent …
- Distinctive: line 41
Keep it one to two screens.
- Distinctive: line 43
Verify AGENTS.md links the map at its configured location.
- Distinctive: line 52
Never record secrets, credentials, or tokens.
- Distinctive: line 53
Do not change AGENTS.md beyond the map link without approval.
- Distinctive: line 54
If the map's configured location is unclear, ask instead of creating a second map.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project map
Purpose
Create or update the project map — the concise orientation artifact
(default <harness-dir>/context/project-map.md) that tells the agent where things
live without loading many files. See DOCUMENTATION.html §16 in the kit.
When to use
- The map does not exist (generation was deferred at onboarding).
- A top-level or load-bearing directory was added, renamed, or removed.
- An entrypoint moved, or build/test/lint commands changed.
- A new protected area or generated path appeared.
- The map demonstrably disagrees with the repository.
When not to use
- Routine file additions inside existing directories.
- As a substitute for reading actual code when implementing.
Required inputs
- The map template (
templates/project-map.md.templatein the kit, or the existing generated map). - Repository inspection: directory tree (depth 2–3), package manifests, scripts, CI config, docs.
- The project
AGENTS.mdprotected-areas section.
Procedure
- Inspect the repository (prefer a subagent if the survey is large).
- Fill or update the map's eight sections: tree, entrypoints, commands, framework/runtime assumptions, important docs, protected areas, SDD locations, generated/do-not-edit files.
- Keep it one to two screens; annotate, do not enumerate.
- Record unknown commands as
TODO: ask the developer— never invent. - Verify
AGENTS.mdlinks the map at its configured location.
Output artifact
The project map file at its configured location (default
<harness-dir>/context/project-map.md).
Safety constraints
- Never record secrets, credentials, or tokens.
- Do not change
AGENTS.mdbeyond the map link without approval. - If the map's configured location is unclear, ask instead of creating a second map.
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.