agentleFS
pragyesh85-SPTpragyesh85-SPT/The-heritage-of-fable5/skills/brain/SKILL.md

brain

Skill1 starsChanged 4 months agoMITView on GitHub

Boot into the CLAUDE-BRAIN inheritance vault (E:/PRAGYESH - WORK/CLAUDE-BRAIN) before doing any work. Use at the start of any session or task in E:/PRAGYESH - WORK — building, fixing, auditing, researching, designing. Loads the vault's core behavior contract, routes to the ONE workflow doc matching the task, and enforces the sleep protocol (write-back) before ending.

25 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    First tenure only: if you (this model identity) have never booted the vault before, also read craft\C00-READ-ME-FIRST.md and …

    line 21
  2. Very specific:

    If the task concerns an existing project: read its card in _REGISTRY\ (find it via _REGISTRY\INDEX.md), plus _REGISTRY\TIP-ECOSYSTEM.md if …

    line 25
  3. Very specific:

    Route the task: read workflows\INDEX.md and load the ONE W-doc whose trigger matches the task.

    line 28
  4. Very specific:

    No W-doc matches → read craft\C13-HOW-I-THINK.md and run its meta-procedure: do the task with the ten patterns, then WRITE the missing …

    line 31
  5. Distinctive:

    Update in place; never fork or copy the vault.

    line 47
  6. Distinctive:

    If a vault instruction conflicts with reality (file moved, API changed), fix the vault as part of the task and note the fix to the user.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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
SKILL.md

/brain — Boot the CLAUDE-BRAIN vault

You are inheriting a knowledge vault written by a predecessor model for this specific user (a non-technical founder). The vault compensates for whatever you lack — follow its procedures over your own instincts wherever they conflict.

Vault root: E:\PRAGYESH - WORK\CLAUDE-BRAIN

Boot sequence (do exactly this, in this order)

  1. Read HOME.md at the vault root. It is the entry point and defines the four layers. Obey its load order.
  2. Read 10-OPERATING-PARAMETERS.md and set the dials for the task at hand. State your dial settings in one line to the user.
  3. First tenure only: if you (this model identity) have never booted the vault before, also read craft\C00-READ-ME-FIRST.md and craft\C11-TIER-GAP-COMPENSATION.md now, and skim the craft titles. Craft docs are read once per model tenure, not per session.
  4. If the task concerns an existing project: read its card in _REGISTRY\ (find it via _REGISTRY\INDEX.md), plus _REGISTRY\TIP-ECOSYSTEM.md if the project is part of TIP. Follow the linked notes per the W83 wake-up protocol.
  5. Route the task: read workflows\INDEX.md and load the ONE W-doc whose trigger matches the task. Do NOT load multiple W-docs or browse the vault — the index exists so you load ~3–5 files total, never all of them.
    • No W-doc matches → read craft\C13-HOW-I-THINK.md and run its meta-procedure: do the task with the ten patterns, then WRITE the missing W-doc and add its INDEX line.
  6. Do the work under the loaded procedure. Core rules that always apply:
    • Final gate (08-FINAL-GATE.md) runs on every answer before sending.
    • Forbidden zone (payments, auth, security rules, migrations, deletes, cross-repo writes): propose, never execute without explicit approval.
    • Delegating to a cheap model → build the envelope from workflows\W84, orchestrate per workflows\W94.
  7. Sleep protocol (mandatory, before ending the session): per W83, write back decisions, learnings, and state changes to the matching registry card or W-doc. Any mistake the user corrected becomes a rule in the matching file (template H in 09-PROMPT-TEMPLATES.md) — update in place, never duplicate. A session that doesn't write back steals from the next one.

Rules about the vault itself

  • Update in place; never fork or copy the vault.
  • New links use [[wikilinks]] matching exact filenames (no extension), added under the ## Linked footer of each touched file.
  • If a vault instruction conflicts with reality (file moved, API changed), fix the vault as part of the task and note the fix to the user.

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.