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.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- compile-wikiSkill
- ingest-sourcesSkill
- lint-healSkill
- qa-agentSkill
- render-outputSkill
- research-workflowSkill
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
- Very specific: line 13
Treat data/raw/ as immutable source evidence.
- Very specific: line 14
Treat notes/ as the curated Obsidian vault.
- Very specific: line 15
Treat research/ as the active run workspace for resumable research jobs, not as a substitute for the curated vault.
- Distinctive: line 16
Prefer updating existing concept pages instead of creating duplicates.
- Distinctive: line 17
Keep always-on instructions short.
- Distinctive: line 18
Every concept page should link to related pages and relevant source summaries.
- Distinctive: line 20
Do not silently invent citations.
- Distinctive: line 21
Treat imported model-generated reports as leads that must be verified against primary sources before they can shape concept pages.
- Distinctive: line 22
If a question cannot be answered from the vault, say so and propose the minimum fetch needed.
- Very specific: line 25
Read relevant source summaries in notes/Sources/.
- Very specific: line 26
Read the linked concept pages in notes/Concepts/.
- Very specific: line 27
Use notes/Runbooks/Agent_Workflow_Quick_Reference.md when you need command syntax or command order.
- Distinctive: line 29
If the answer yields durable knowledge, file it back into the vault.
- Very specific: line 30
Run lint after structural edits.
- Very specific: line 31
Update notes/Home.md and notes/TODO.md when the vault's structure or gaps change.
- Very specific: line 34
When a topic needs a full research run, use the resumable workflow in research/:
- Distinctive: line 35
create a brief, status checkpoint, and progress log
- Distinctive: line 38
write findings, run a contrarian review, then draft the final report
- Very specific: line 52
Use the skills in skills/ when relevant:
- Distinctive: line 65
Use Obsidian-style wikilinks for internal note links when editing curated notes.
- Distinctive: line 66
Keep note filenames stable and human-readable.
- Distinctive: line 67
Prefer frontmatter on durable notes so properties remain queryable in Obsidian.
≈ “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.
Files
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:
- reference existing vault notes, or
- 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
- Read relevant source summaries in
notes/Sources/. - Read the linked concept pages in
notes/Concepts/. - Use
notes/Runbooks/Agent_Workflow_Quick_Reference.mdwhen you need command syntax or command order. - Answer from the vault.
- If the answer yields durable knowledge, file it back into the vault.
- Run
lintafter structural edits. - Update
notes/Home.mdandnotes/TODO.mdwhen 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_tierasfast,standard, ordeep - 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-sourcescompile-wikilint-healqa-agentrender-output
Reference notes
notes/Runbooks/Agent_Workflow_Quick_Reference.mdnotes/Concepts/Workflow_Pattern_Inventory.mdkops 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.
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.

