knowledge-layers
Skill2 starsChanged 24 days agoApache-2.0View on GitHub
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Abdullokh-N/proza-rutheir own version, first seen Aug 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Abdullokh-N/proza-ru★ 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 repository33 other files it gives its agents.
- character-simSkill
- cold-readSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-modesSkill
- creative-writing-museSkill
- demolitionSkill
- exportSkill
- gatesSkill
- grill-with-docsSkill
- information-hierarchySkill
- intent-modelingSkill
- kb-integritySkill
- kb-managementSkill
- llm-writingSkill
- md-validationSkill
- project-setupSkill
- qi-layerSkill
- reader-simSkill
- reflectSkill
- series-bibleSkill
- seriesSkill
- shared-daoSkill
- story-ledgersSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- structured-artifactSkill
- style-guardrailsSkill
- voiceSkill
- writing-principlesSkill
- writing-staffingSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If it's intent/mental-model for a directory → AGENTS.md.
- Very specific: line 26
If it's directory-scoped depth an agent looks up → .context/.
- Very specific: line 27
If it's deferred work scoped to this directory → .context/TODO (must-do) or .context/FUTURE (nice-to-have).
- Very specific: line 31
If it's big picture — cross-cutting decisions, domain concepts, higher-level system architecture → KB.
- Very specific: line 33
If it's for end users → docs/.
- Distinctive: line 34
If it's a temporary work artifact → work directory.
- Very specific: line 36
When in doubt, colocate. Knowledge that depends on one subsystem belongs in that subsystem's AGENTS.md or .context/ even when it reads like …
- Very specific: line 45
Every durable layer — AGENTS.md, .context/, KB, docs/ — holds the best current understanding.
- Distinctive: line 59
Git history is the archive: Commit untracked files before deleting them so the removal lands in history, and say what was removed and why …
- Very specific: line 90
Follow /information-hierarchy.
- Distinctive: line 102
Maintain: keep the wiki current per Current Truth Over History above.
≈ “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.
Files
Knowledge Layers
Load /qi-layer when writing or editing AGENTS.md or .context/ files: it
owns the craft (four principles, contents guidelines, what doesn't belong).
Load /information-hierarchy if not already loaded for disclosure tiers.
Load /llm-writing if not already loaded.
The Five Layers
| Layer | What it holds | When to use it |
AGENTS.md | Intent and mental model for a directory | First thing agents read on entry; what to understand before working here |
.context/ | Contracts, architecture, rationale (CONTEXT.md); deferred work (TODO, FUTURE) | Reference depth and tracked deferrals, co-located with the code they describe |
| KB | Cross-cutting decisions, domain concepts, patterns | Spans directories; outlives sessions; no single directory owns it |
docs/ | User-facing documentation | Different audience, different update cadence |
| Work directory | Temporary design decisions and scratch | Not colocated with durable content; scoped to an active work item |
Placement Rules
If it's intent/mental-model for a directory → AGENTS.md.
If it's directory-scoped depth an agent looks up → .context/.
If it's deferred work scoped to this directory → .context/TODO (must-do)
or .context/FUTURE (nice-to-have). Flat markdown lists — each entry names
the affected path and concrete follow-up. Cross-cutting items or items needing
external visibility get filed in the project's issue tracker instead.
If it's big picture — cross-cutting decisions, domain concepts,
higher-level system architecture → KB.
If it's for end users → docs/.
If it's a temporary work artifact → work directory.
When in doubt, colocate. Knowledge that depends on one subsystem belongs in that subsystem's AGENTS.md or .context/ even when it reads like a concept; the KB stays code-agnostic, holding what survives implementation change. Knowledge that lives far from what it describes rots faster: changes to the code don't trigger awareness that a distant doc needs updating.
Current Truth Over History
Every durable layer — AGENTS.md, .context/, KB, docs/ — holds the best
current understanding; work directories may keep intermediate reasoning
while their work item is active. When durable content is
superseded, delete it or (for KB pages) move it to archive/
(.kgignore'd, excluded from the knowledge graph). Live content never
references archived content. Pages read as current truth, never narrate
their own evolution.
Deletion needs no replacement. A page whose subject is gone, or that describes behavior the system no longer has, gets deleted on sight — even with nothing new to write in its place. Stale knowledge is worse than a gap: agents load it and reason from it. Deletion is the content-truth owner's call; structural roles flag instead.
Git history is the archive. Commit untracked files before deleting them so the removal lands in history, and say what was removed and why in the commit message. Deletion is cheap because nothing tracked is ever truly lost.
Truth is anchored per layer. AGENTS.md and .context/ describe the
checkout that contains them: update them in the same branch as the code
change and let the merge carry both — with parallel PRs in flight, each
branch documents itself. The KB is code-agnostic: it records the current
settled intent — what the system should be — and a settled decision is KB
truth the moment it's made, merged or not. Unsettled intent isn't KB
material; it stays in the work directory. docs/ describes shipped
behavior.
Decision records are the exception: preserve superseded decisions in place when they explain why the system changed. Mark the old decision as superseded and link to the replacement.
KB Conventions
Structure
The KB is a directory tree like any other: it carries its own AGENTS.md
and .context/ pair, written per /qi-layer — intent in AGENTS.md,
governance depth (writing conventions, structure, validation) in
.context/. Read the KB's own AGENTS.md before writing. Treat this
skill as the cross-project default; the local KB guide wins for that KB.
See resources/bootstrap.md for a suggested starting layout.
Wiki Page Conventions
Follow /information-hierarchy. One concept per document; name files by
what they describe (token-validation.md), not when (auth-redesign-notes.md).
Cross-reference instead of re-explaining. Load /shared-dao for vocabulary
methodology. Use mermaid for anything spatial; capture what code can't
easily tell you.
Operations
Ingest: new information enters the KB. Read the source, extract key knowledge, write or update wiki pages, and update indexes/cross-links touched by the change.
Maintain: keep the wiki current per Current Truth Over History above.
Lint: health-check the wiki. Look for contradictions, stale claims,
orphan pages, missing cross-references. Use /md-validation for link
checking and diagram validation.
Flag content needing human attention with > [!FLAG] **Needs human review**.
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.