agentleFS
Sign inStart free
manazoid4manazoid4/maz-works-knowledge-vault/CLAUDE.md

maz-works-knowledge-vault

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

The unified Maz Works vault lives at C:\Users\manaz\Desktop\Maz Works Knowledge Vault and is mirrored at <https://github.com/manazoid4/maz-works-knowledge-vault>. It covers every Maz Works project, client engagement, experiment, research thread, reusable delivery pattern, and agent handoff. JobFilter is one project inside the system. The active Claude Code package is maz-works-knowledge-vault. Upstream MIT attribution is in ATTRIBUTION.md.

The file

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

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    YouTube URL from Maz → video intelligence: follow prompts/youtube-video-intelligence.md (full transcript, facts vs opinion vs inference, …

    line 11
  2. Very specific:

    Read the relevant project folder under wiki/projects/.

    line 20
  3. Very specific:

    Read wiki/hot.md when recent cross-project context matters.

    line 21
  4. Very specific:

    Read a selected skill's complete SKILL.md before applying it.

    line 22
  5. Distinctive:

    Use the canonical vault; do not create a competing general vault.

    line 50
  6. Distinctive:

    Keep historical or upstream names only where provenance requires them.

    line 51
  7. Distinctive:

    Never store credentials, private client information, or private spiritual content.

    line 52
  8. Distinctive:

    Use file locking for concurrent wiki writes.

    line 53
  9. Very specific:

    Run make test after changing scripts or skills.

    line 54

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

Maz Works Knowledge Vault — Claude Instructions

The unified Maz Works vault lives at C:\Users\manaz\Desktop\Maz Works Knowledge Vault and is mirrored at https://github.com/manazoid4/maz-works-knowledge-vault.

It covers every Maz Works project, client engagement, experiment, research thread, reusable delivery pattern, and agent handoff. JobFilter is one project inside the system.

Maz Works sales: start here (every agent)

  • Focus: NOW.md (3 projects only)
  • Lead rules: Lead Quality v2 (problem → evidence → paid intervention; gates; Gold/Silver/Bench; Gold does not need a Ltd) + hand-off format: prompts/maz-works-niche-needs.md. Offers/prices only from mazos-site/app/offers.ts.
  • YouTube URL from Maz → video intelligence: follow prompts/youtube-video-intelligence.md (full transcript, facts vs opinion vs inference, connect to our projects, save a note in wiki/sources/video-intelligence/, commit knowledge: ingest YouTube research - <title>). Search wiki/sources/video-intelligence/_index.md before new research or a related strategic decision.
  • Prompt library + /mw-* commands: prompts/maz-works-prompt-library.md
  • LinkedIn posts: prompts/maz-works-linkedin-launch.md
  • Leads, call list, pitches: PRIVATE repo https://github.com/manazoid4/maz-works-leads (local: leads/, git-ignored here). Never copy lead data into this public repo.
  • Give leads to the owner as plain-text blocks (Google Docs format in niche-needs). Keep replies short.

Begin a session

  1. Read AGENTS.md.
  2. Read the relevant project folder under wiki/projects/.
  3. Read wiki/hot.md when recent cross-project context matters.
  4. Read a selected skill's complete SKILL.md before applying it.

Vault structure

  • .raw/ — immutable source documents
  • wiki/ — maintained cross-project knowledge
  • wiki/projects/ — project-specific truth and status
  • wiki/sessions/ — durable session receipts
  • Local Knowledge/ — ingestion, graph, retrieval, and digest tools
  • Personal/ — personal notes
  • Archive/ — retained history, not current truth

Available workflows

  • /wiki — setup and vault routing
  • /wiki-ingest — source ingestion
  • /wiki-query — cited answers from vault material
  • /wiki-lint — health checks
  • /wiki-cli — Obsidian transport
  • /wiki-retrieve — hybrid retrieval
  • /wiki-mode — LYT, PARA, Zettelkasten, or Generic routing
  • /save — durable session note
  • /autoresearch — bounded research loop
  • /canvas — Obsidian Canvas work
  • /think — structured reasoning loop

Guardrails

  • Use the canonical vault; do not create a competing general vault.
  • Keep historical or upstream names only where provenance requires them.
  • Never store credentials, private client information, or private spiritual content.
  • Use file locking for concurrent wiki writes.
  • Run make test after changing scripts or skills.

The active Claude Code package is maz-works-knowledge-vault. Upstream MIT attribution is in ATTRIBUTION.md.

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.

Check your setup, free