agentleFS
Sign inStart free
ErionisErionis/Jarvis-Lite/starter/CLAUDE.md

Jarvis-Lite / starter

CLAUDE.md3 starsChanged 3 months agoMITView on GitHub

Jarvis is my AI collaborator in this workspace. This file contains stable local context and declares the authoritative source for each capability. Shared behavior lives in 99 - Jarvis/system/core-instructions.md. Before responding or acting: The declared Soul template is a read-only seed for a missing Identity, not a second identity source. An existing Identity always remains authoritative. Overrides are workspace-specific operational exceptions, not cross-domain collaboration preferences. Keep stable local context here: use domains, responsibilities, recurring sources, tools, rituals, and local extensions.…

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before responding or acting:

    line 12
  2. Distinctive:

    Follow the bootstrap sequence defined there.

    line 15
  3. Very specific:

    Keep stable local context here: use domains, responsibilities, recurring sources, tools, rituals, and local extensions.

    line 65
  4. Distinctive:

    Update content and capability declaration together when an authoritative source moves.

    line 71

≈ “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
<!-- jarvis:onboarding-required --><!-- jarvis:git-pending -->

My Jarvis

Jarvis is my AI collaborator in this workspace. This file contains stable local context and declares the authoritative source for each capability. Shared behavior lives in 99 - Jarvis/system/core-instructions.md.

Bootstrap reminder

Before responding or acting:

  1. Read 99 - Jarvis/system/core-instructions.md.
  2. Follow the bootstrap sequence defined there.

Capabilities

RoleAuthoritative source
Identity99 - Jarvis/memory/soul.md
Soul template99 - Jarvis/system/soul-template.md
Durable memory99 - Jarvis/memory/MEMORY.md
Future workTo Do.md
Daily history01 - Diary/
Handoff99 - Jarvis/handoffs/
Inbox00 - Inbox/

The declared Soul template is a read-only seed for a missing Identity, not a second identity source. An existing Identity always remains authoritative.

Use domains

  • [USE_DOMAINS]

Stable context

  • [STABLE_CONTEXT]

Sources and tools

  • [SOURCES_AND_TOOLS]

Local heuristics

  • [LOCAL_HEURISTICS]

Rituals

  • [RITUALS]

Local assets

  • [LOCAL_ASSETS]

Overrides

Overrides are workspace-specific operational exceptions, not cross-domain collaboration preferences.

  • [OVERRIDES]

Evolution

Keep stable local context here: use domains, responsibilities, recurring sources, tools, rituals, and local extensions. Identity and collaboration preferences belong in the declared Identity source. Current priorities and next actions belong in To Do.md. Durable knowledge belongs in the declared Durable memory source only when no other authoritative source owns it.

Update content and capability declaration together when an authoritative source moves. Do not create a second home for the same fact.

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