agentleFS
arnaudgelasarnaudgelas/K-Ops/.claude/CLAUDE.md

K-Ops

CLAUDE.md1 starsChanged 7 months agoMITView on GitHub

This repository is an Obsidian-aligned living research vault. The same operating contract should work whether the active CLI is Claude Code, Codex CLI, or Gemini CLI. Canonical rules: see OPERATING_RULES.md.

The file

Show its rules and text

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

22 rules. About 0 are common, 12 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat data/raw/ as immutable source evidence.

    line 13
  2. Very specific:

    Treat notes/ as the curated Obsidian vault.

    line 14
  3. Very specific:

    Treat research/ as the active run workspace for resumable research jobs, not as a substitute for the curated vault.

    line 15
  4. Distinctive:

    Prefer updating existing concept pages instead of creating duplicates.

    line 16
  5. Distinctive:

    Keep always-on instructions short.

    line 17
  6. Distinctive:

    Every concept page should link to related pages and relevant source summaries.

    line 18
  7. Distinctive:

    Do not silently invent citations.

    line 20
  8. Distinctive:

    Treat imported model-generated reports as leads that must be verified against primary sources before they can shape concept pages.

    line 21
  9. Distinctive:

    If a question cannot be answered from the vault, say so and propose the minimum fetch needed.

    line 22
  10. Very specific:

    Read relevant source summaries in notes/Sources/.

    line 25
  11. Very specific:

    Read the linked concept pages in notes/Concepts/.

    line 26
  12. Very specific:

    Use notes/Runbooks/Agent_Workflow_Quick_Reference.md when you need command syntax or command order.

    line 27
  13. Distinctive:

    If the answer yields durable knowledge, file it back into the vault.

    line 29
  14. Very specific:

    Run lint after structural edits.

    line 30
  15. Very specific:

    Update notes/Home.md and notes/TODO.md when the vault's structure or gaps change.

    line 31
  16. Very specific:

    When a topic needs a full research run, use the resumable workflow in research/:

    line 34
  17. Distinctive:

    create a brief, status checkpoint, and progress log

    line 35
  18. Distinctive:

    write findings, run a contrarian review, then draft the final report

    line 38
  19. Very specific:

    Use the skills in skills/ when relevant:

    line 52
  20. Distinctive:

    Use Obsidian-style wikilinks for internal note links when editing curated notes.

    line 65
  21. Distinctive:

    Keep note filenames stable and human-readable.

    line 66
  22. Distinctive:

    Prefer frontmatter on durable notes so properties remain queryable in Obsidian.

    line 67

≈ “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

This repository is an Obsidian-aligned living research vault. The same operating contract should work whether the active CLI is Claude Code, Codex CLI, or Gemini CLI.

Canonical rules: see OPERATING_RULES.md.

Mission

Turn raw sources into a durable Markdown knowledge base. Every answer should either:

  1. reference existing vault notes, or
  2. improve the vault if durable new knowledge was produced.

Operating rules

  • Treat data/raw/ as immutable source evidence.
  • Treat notes/ as the curated Obsidian vault.
  • Treat research/ as the active run workspace for resumable research jobs, not as a substitute for the curated vault.
  • Prefer updating existing concept pages instead of creating duplicates.
  • Keep always-on instructions short; move command detail into runbooks, skills, or templates.
  • Every concept page should link to related pages and relevant source summaries.
  • Record contradictions, uncertainties, and missing evidence explicitly.
  • Do not silently invent citations.
  • Treat imported model-generated reports as leads that must be verified against primary sources before they can shape concept pages.
  • If a question cannot be answered from the vault, say so and propose the minimum fetch needed.

Default workflow

  1. Read relevant source summaries in notes/Sources/.
  2. Read the linked concept pages in notes/Concepts/.
  3. Use notes/Runbooks/Agent_Workflow_Quick_Reference.md when you need command syntax or command order.
  4. Answer from the vault.
  5. If the answer yields durable knowledge, file it back into the vault.
  6. Run lint after structural edits.
  7. Update notes/Home.md and notes/TODO.md when the vault's structure or gaps change.

Research runs

When a topic needs a full research run, use the resumable workflow in research/:

  • create a brief, status checkpoint, and progress log
  • record the quality_tier as fast, standard, or deep
  • collect sources into notes/Sources/
  • write findings, run a contrarian review, then draft the final report
  • archive completed runs with a manifest that lists every moved artifact

Page conventions

Each concept page should usually contain:

  • What it is
  • Why it matters
  • Key claims
  • Evidence / source basis
  • Related concepts
  • Open questions
  • Backlinks

Skills

Use the skills in skills/ when relevant:

  • ingest-sources
  • compile-wiki
  • lint-heal
  • qa-agent
  • render-output

Reference notes

  • notes/Runbooks/Agent_Workflow_Quick_Reference.md
  • notes/Concepts/Workflow_Pattern_Inventory.md
  • kops bootstrap --target <dir>

Obsidian conventions

  • Use Obsidian-style wikilinks for internal note links when editing curated notes.
  • Keep note filenames stable and human-readable.
  • Prefer frontmatter on durable notes so properties remain queryable in Obsidian.

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.