Give your AI a memory.

Your AI forgets everything the moment you start a new chat. The project you described yesterday, the correction you gave twice last week, the way you like things done: gone, and you type it all again.

This fixes it with files rather than software. A small folder of plain text your AI reads before you type a word, so every session starts already knowing who you are, what you are working on and how you want things done.

It is the system Sean has run across an agency, a personal brand and about twenty projects for months, with every private detail stripped out. What is left is the templates and the operating rules.

You need an AI that reads files on your computer, and about fifteen minutes to set it up.

Download it.

One folder, 24 KB: the four template files, the example memories, the docs and the licence.

Download the system

If you already use git you can skip the download and clone it in one line instead.

Clone it in one line.

git clone https://github.com/seanng23/claude-memory-system

HOW TO SET IT UP

How to set it up.

Unzip it and copy the templates in.
Copy the files in the templates folder into the root of the folder you work in, along with the memory folder that comes with them.
Fill in the blanks.
Open the standing instructions file and replace the placeholders with your own business: who you are, how you want work done, where things live. Fifteen minutes here beats an hour of prompting later.
Write your first three memories.
Three, not thirty. The four example files show you the shape. After that the system grows as you work, one fact at a time.

WHAT IS INSIDE

What is inside.

One giant instruction file gets skimmed, and the most important line gets the same attention as the least. So the system splits your business across files by how often each one changes.

Standing instructions.: Who you are, how you want work done and where things live. Loaded automatically at the start of every session, so you stop re-explaining your standards.
The hot cache.: What is live right now and the next action on each thread. It has a hard size limit so it stays readable, and it is the first thing your AI reads.
The map.: The index that routes to everything else. One line per folder, so your AI knows where to look instead of searching blind.
Memory files.: One durable fact per file: a correction you gave, a preference, a gotcha about a tool. Each fact lives in exactly one place, and everything else points at it.
The session log.: What each session produced and decided, newest first. It is how this week's AI knows what last week's AI did.
The upkeep rules.: Two rules carry the whole system. Any session that changes your situation updates the hot cache before it closes, and a correction you give twice gets written down with the why.

BEFORE YOU START

What you need.

An AI that reads files.: Claude Code, Claude Desktop, Cursor, Codex or anything else that reads a project file. The files are plain text, so if you change tools tomorrow the system comes with you.
About fifteen minutes.: The setup is copying one folder and filling in the placeholders. Everything after that is habit rather than work.
Nothing to pay for.: No plugin, no database, no subscription and no key to add. It is four markdown files and the rules for keeping them true.

MIT licensed. Take it, strip it, rename it, sell what you build with it. The source and the full docs are on GitHub.

LEVEL TWO

This is level two of the method.

Level two is your business written down so AI can read it. Writing it down once is the easy half. This system is the other half: the files stay current as you work, so what your AI knows about you grows instead of going stale.

See what we do

Starting from nothing written down at all? The Vault Prompt interviews you and writes your first files for you.