agentleFS
sammcjsammcj/agentic-coding/Skills/llm-wiki/examples/CLAUDE.md

agentic-coding / examples

CLAUDE.md167 starsChanged 10 days agoApache-2.0View on GitHub

This repository is an LLM wiki: a knowledge base on transformer architectures, attention cost and efficiency, and long-context scaling, compiled into plain markdown under wiki/ and maintained by an AI agent at the user's direction - the user curates sources and asks questions; the agent does the bookkeeping. To work with it, start by reading SKILL.md in this directory - it explains how to query the wiki and the conventions to follow. The article catalogue is wiki/index.md; the format is…

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

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always use Australian English spelling.

    line 23
  2. Distinctive:

    Always use plain ASCII punctuation (straight quotes, single hyphens), Do NOT use any "smart" formatting such as smart quotes, em-dashes, …

    line 24
  3. Distinctive:

    When you have completed all work, you may wish to ask the user if they'd like you to commit your changes to git, if doing so ensure your …

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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

Machine Learning Wiki

<!-- Note this is an EXAMPLE CLAUDE.md file for the EXAMPLE llm-wiki -->

This repository is an LLM wiki: a knowledge base on transformer architectures, attention cost and efficiency, and long-context scaling, compiled into plain markdown under wiki/ and maintained by an AI agent at the user's direction - the user curates sources and asks questions; the agent does the bookkeeping.

To work with it, start by reading SKILL.md in this directory - it explains how to query the wiki and the conventions to follow. The article catalogue is wiki/index.md; the format is described in wiki/README.md.

If the llm-wiki skill is available and not already active, activate it. It owns the workflow for every change to the wiki - ingesting sources, superseding stale knowledge, linting, auditing - and keeps the format consistent. Without it, treat the wiki as read-only and do not hand-edit articles outside the wiki/README.md conventions. raw/ is immutable source material.

Scope

  • Mode: personal
  • Purpose: track how transformer architectures scale, and what the cost of attention means in practice.
  • In scope: transformer internals, attention cost and efficiency, long-context scaling, and the papers and posts behind them.
  • Out of scope: model release news, vendor benchmarks, and anything about running or serving models in production.
  • Horizon: ongoing.

Check an incoming source against this before ingesting it. A source outside the scope is a conversation with the user, not a judgement call to make silently. If the wiki has genuinely outgrown this block, say so and let the user decide whether to widen the scope or start a separate wiki - do not widen it yourself.

General rules

  • Always use Australian English spelling.
  • Always use plain ASCII punctuation (straight quotes, single hyphens), Do NOT use any "smart" formatting such as smart quotes, em-dashes, en-dashes or non-breaking spaces.

Git commits

When you have completed all work, you may wish to ask the user if they'd like you to commit your changes to git, if doing so ensure your git commit message is clear and concise as to what has been added or improved.

(Sample note: this example wiki lives in examples/ within the llm-wiki repo.)

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.