agentleFS
artificialbeingzartificialbeingz/abz-karpathy-llm-wiki/CLAUDE.md

abz-karpathy-llm-wiki

CLAUDE.md1 starsChanged 6 months agoMITView on GitHub

Schema for the LLM Wiki. Read on every session. This is not a skill. It is the agent's default behavior, on every action. Skip it only when the user explicitly says "answer from general knowledge" or "don't check the wiki." Default to synthesis. Fewer pages with more cross-links beats many sparse pages.

The file

Show its rules and text

We split this CLAUDE.md into the rules it gives an agent

13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before answering any question, drafting any document, or making any decision:

    line 29
  2. Very specific:

    Read wiki/index.md to find what's available

    line 30
  3. Distinctive:

    Read relevant synthesis pages and deep-dives

    line 31
  4. Very specific:

    If the wiki has gaps for the question, fall back to raw/

    line 32
  5. Distinctive:

    If you discover something durable while answering, file it back into the wiki

    line 33
  6. Distinctive:

    Default to synthesis. Fewer pages with more cross-links beats many sparse pages.

    line 41
  7. Distinctive:

    Every page uses YAML frontmatter:

    line 47
  8. Distinctive:

    When ingestion finds a contradiction, flag it inline using this exact format:

    line 58
  9. Distinctive:

    Do not silently overwrite.

    line 63
  10. Very specific:

    Add your own SKILL.md files in .claude/skills/<skill-name>/ to extend.

    line 70
  11. Distinctive:

    Read the wiki before doing work

    line 73
  12. Distinctive:

    Update the wiki after doing work

    line 74
  13. Distinctive:

    Create deep-dive pages by default — bias toward synthesis updates

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

Schema for the LLM Wiki. Read on every session.

What this is

A wiki built and maintained collaboratively by a human and an LLM agent. The wiki shapes itself around whatever sources you feed it — legal cases, medical research, code documentation, customer interviews, anything. Drop sources in raw/. The agent distills them into wiki/. You query the wiki before doing work.

Architecture — three layers

  1. raw/ — immutable sources. Files only move from unprocessed/ to processed/ during ingestion; content is never modified.
  2. wiki/ — agent-owned synthesis. Create, update, cross-link freely.
  3. CLAUDE.md — schema. Rules and pointers.

Directory layout

.
├── CLAUDE.md
├── .claude/skills/        skills (ingest-source, lint-wiki, save-session)
├── raw/
│   ├── unprocessed/       queue of new sources awaiting ingestion
│   ├── processed/         sources after ingestion
│   └── session-summary/   chronological session records
└── wiki/
    ├── index.md           catalog of all wiki pages (one-line entries by category)
    ├── log.md             append-only operations log (ingests, refactors, lint passes)
    └── _templates/        page templates (copy when creating new pages)

The query rule (always on)

Before answering any question, drafting any document, or making any decision:

  1. Read wiki/index.md to find what's available
  2. Read relevant synthesis pages and deep-dives
  3. If the wiki has gaps for the question, fall back to raw/
  4. If you discover something durable while answering, file it back into the wiki

This is not a skill. It is the agent's default behavior, on every action. Skip it only when the user explicitly says "answer from general knowledge" or "don't check the wiki."

Two output shapes — synthesis vs deep-dive

  • Synthesis page — catalog-style, covers many entities of one type. Lives at wiki/<category>.md. Default choice.
  • Deep-dive page — detailed coverage of one entity. Lives at wiki/<category>/<name>.md. Created only when content has design-level depth that won't fit a synthesis row.

Default to synthesis. Fewer pages with more cross-links beats many sparse pages.

Page types

The agent invents page types from your sources. A legal wiki grows case, ruling, and precedent pages; a medical wiki grows study and cohort pages; an engineering wiki grows pipeline, table, and concept pages. When a structure repeats, the agent creates a template in wiki/_templates/. Default templates (concept, decision, plan, reference) are starting examples — extend, replace, or remove them.

Frontmatter conventions

Every page uses YAML frontmatter:

---
type: <page type>
status: draft | partial | complete | current
last_updated: YYYY-MM-DD
sources: [list of source paths]
---

Conflict callout format (mandatory)

When ingestion finds a contradiction, flag it inline using this exact format:

⚠️ Conflict noted YYYY-MM-DD — <one-line title>

  • Source A (<path>): <claim>
  • Source B (<path>): <claim>
  • Resolution: (empty until resolved) Do not silently overwrite. Do not pause to ask the user.

Skills

Procedures live in .claude/skills/:

  • ingest-source — process raw sources into the wiki (interactive or bulk)
  • lint-wiki — audit wiki for stale pages, contradictions, orphans
  • save-session — capture session summary to raw/session-summary/ Add your own SKILL.md files in .claude/skills/<skill-name>/ to extend.

Workflow rules

  • Read the wiki before doing work
  • Update the wiki after doing work
  • Distinguish raw from synthesis (raw stays in raw/, distilled goes in wiki/)
  • Flag, don't overwrite (use conflict callouts)
  • One thing per page (one entity, one concept, one decision)
  • Standard markdown links (not [[wikilinks]])

What this agent does NOT do

  • Modify content of files in raw/ (read-only; only moved between unprocessed/ and processed/)
  • Auto-fix structural wiki issues without confirmation
  • Create deep-dive pages by default — bias toward synthesis updates

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.