feature-map
Skill320 starsChanged 8 days agoMITView on GitHub
Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break. Use it before changing a feature, when reviewing a diff or PR, and when asked what a feature does or how parts connect.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- leather-io/monotheir own version, first seen Nov 2, 2026
- langwatch/langwatchtheir own version, first seen Oct 8, 2026
- onyx-dot-app/onyxword for word, first seen Oct 8, 2026
- markphelps/agent-pluginstheir own version, first seen Sep 28, 2026
Other versions4 projects use a version of this.
Word for word · 1
- onyx-dot-app/onyx★ 33k100% same
Edited · 0
None found.
Wrote their own version · 3
- langwatch/langwatch★ 5ksame name
- leather-io/mono★ 28same name
- markphelps/agent-plugins★ 6same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend/AGENTS.mdAGENTS.md
- documentation/AGENTS.mdAGENTS.md
- mobile/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- docs-writingSkill
- merge-dependabot-prsSkill
- onyx-craft-devSkill
- onyx-dev-stackSkill
- playwright-e2e-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Before you trust a name, read .agents/feature-map/GLOSSARY.md.
- Very specific: line 25
Read the component document under .agents/feature-map/components/.
- Very specific: line 34
Follow .agents/feature-map/VERIFYING.md step by step.
- Very specific: line 38
When you end a turn, the Stop hook may block once with an editing brief.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Onyx feature map
.agents/feature-map/ records how Onyx works: where each responsibility lives,
how the parts connect, the rules a change can break, the design reasons, and known
issues. It does not restate the code.
Find the component
- For new work: start at the Common tasks table in
.agents/feature-map/INDEX.mdand at.agents/feature-map/CROSS-CUTTING.md. - From a code path: look it up in
.agents/feature-map/PATHS.md. The longest matching prefix wins. A path under## Not mappedhas no component. A path that no row covers is unmapped: say so, and read the nearest code and tests yourself. - Before you trust a name, read
.agents/feature-map/GLOSSARY.md. Onyx uses words such as Persona, Tool, turn and SearchDoc in more than one sense.
Before you change code
Read the component document under .agents/feature-map/components/.
User experience (or Callers, for a component that other code builds on)
says what the component must do for the people and code that use it. Contracts and traps
come next: these are the rules a change can break without a failing test.
Recipes show how to do common tasks. Follow the [[component]] links in
Dependencies for each area your change reaches.
When you review a diff or PR
Follow .agents/feature-map/VERIFYING.md step by step.
Keep the map true
When you end a turn, the Stop hook may block once with an editing brief. It names
the sections and keys that cite the code you changed. Read only those and the
summary, and answer the questions in "Editing judgment" in
.agents/feature-map/README.md. No update is a normal answer. Do not rewrite
parts the change does not touch. The full rules are in "Keeping the map true".
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.

