agentleFS
puretechnycpuretechnyc/purebrain-skills/skills/operations/build-your-brain/SKILL.md

build-your-brain

Skill0 starsChanged 6 months agoMITView on GitHub

Set up a persistent AI brain using cloud storage. Folder structure, daily feeding habits, retrieval preflight before every task, and weekly maintenance. Storage-agnostic (Google Drive, Dropbox, OneDrive, local folders).

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Every time you complete work, save it.

    line 42
  2. Very specific:

    Naming convention: Use YYYY-MM-DD-topic for time-sensitive items.

    line 52
  3. Very specific:

    Does a deliverable for this already exist?: Search /brain/deliverables/

    line 62
  4. Very specific:

    Is there a documented process?: Search /brain/skills/

    line 63
  5. Very specific:

    What have I learned about this topic?: Search /brain/learnings/

    line 64
  6. Very specific:

    Are there relevant reference docs?: Search /brain/references/

    line 65
  7. Distinctive:

    Fill gaps: If you worked on a topic three times but have no brain doc, write one

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Build Your Brain: Never Lose Context Again

Your AI is only as good as what it remembers. Without a structured brain, every session starts from zero. You re-explain your business, your preferences, your past decisions. With a brain, your AI compounds knowledge over time like a team member who never forgets.

This skill has four parts: Build, Feed, Check, Grow.


1. Build Your Brain (One-Time Setup, ~15 minutes)

Pick your storage. Google Drive, Dropbox, OneDrive, or a local folder all work. The only requirement: your AI can access it.

Create this folder structure:

/brain/
  deliverables/    -- Everything you or your AI produces
  learnings/       -- What you have discovered (domain knowledge, research)
  references/      -- External docs you rely on (brand guides, templates, SOPs)
  context/         -- Business info that rarely changes (brand voice, goals, team)
  skills/          -- Reusable processes (how to write a newsletter, how to onboard)

Then add your starter context. Drop these into /brain/context/:

  • A one-page summary of your business
  • Your brand voice notes
  • Your team roster
  • Your current goals

2. Feed Your Brain (Daily Habit, ~2 minutes per item)

Every time you complete work, save it. Every time you learn something, write it down. If it took effort to create or discover, it goes in the brain.

After this...Save to...Example filename
Finishing a deliverable/brain/deliverables/2026-04-30-client-proposal-acme.md
A meeting/brain/learnings/2026-04-30-client-wants-q3-pivot.md
Finding a useful template/brain/references/email-welcome-sequence-template.md
Making a mistake/brain/learnings/2026-04-30-never-send-invoices-friday.md
Creating a repeatable process/brain/skills/how-to-write-a-case-study.md

Naming convention: Use YYYY-MM-DD-topic for time-sensitive items. Use plain descriptive names for evergreen items.


3. Check Your Brain Before Every Task (Retrieval Preflight)

This is the most valuable habit. Before starting ANY new task, search your brain first. It takes 30 seconds and prevents hours of wasted work.

The four questions:

  1. Does a deliverable for this already exist? Search /brain/deliverables/
  2. Is there a documented process? Search /brain/skills/
  3. What have I learned about this topic? Search /brain/learnings/
  4. Are there relevant reference docs? Search /brain/references/

What this prevents:

  • Rebuilding something that already exists
  • Contradicting a decision you made last month
  • Repeating a mistake you already documented
  • Starting from scratch when a template exists

4. Grow Your Brain (Weekly, ~10 minutes)

Once a week:

  • Organize: Move any files dumped in the wrong folder
  • Archive: Move outdated items to /brain/_archive/
  • Fill gaps: If you worked on a topic three times but have no brain doc, write one
  • Review learnings: Skim this week's entries for patterns worth capturing as skills

Quick-Start Checklist

  • Choose your storage platform
  • Create the 5 folders
  • Add your business summary to /brain/context/
  • Add your brand voice notes to /brain/context/
  • Save your next completed deliverable to /brain/deliverables/
  • Before your next task, run the 4-question preflight check
  • Set a weekly 10-minute calendar reminder for brain maintenance

Why This Works

The average knowledge worker spends 1.8 hours per day searching for information they have seen before (McKinsey). An AI without persistent memory starts from absolute zero every session.

A structured brain turns your AI from a stateless tool into a compounding asset. After 30 days, your AI will know your business well enough to produce first-draft work that needs minimal editing.

The brain is the difference between "AI that helps" and "AI that knows you."


Built by PureBrain -- AI-powered marketing operations.

Want the full suite of 183+ production-tested skills? Start your trial ->

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.