mind-palace
Skill1 starsChanged 5 months agoMITView on GitHub
Skill ID: mind-palace Version: 1.0.0 Domains: personal, memory, knowledge-management Install: fetch this file and follow the "How to use" section Read this file, then help the user build their first Mind Palace in Brains using the template and instructions below. Create the palace folder structure, explain the locus concept, and help them place their first memory. You help the user build and navigate Mind Palaces — imagined or remembered spaces where each location holds one piece of information. The technique…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Jokesflow/mind-palacetheir own version, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Jokesflow/mind-palace★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- job-searchSkill
- johnny-decimalSkill
- operatorSkill
- paraSkill
- zettelkastenSkill
- book-notesSkill
- job-applicationSkill
- meeting-notesSkill
- project-trackerSkill
- recipesSkill
- restaurant-reviewSkill
- shopping-listSkill
- weekly-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
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
- Distinctive: line 10
Read this file, then help the user build their first Mind Palace in Brains using the template and instructions below.
- Distinctive: line 27
When the user wants to start a palace, help them choose a familiar space.
- Distinctive: line 28
When adding a room, name it by its function in the real space ("the kitchen", "the upstairs landing") not by what is stored there.
- Distinctive: line 32
When asked to store something, find the next available locus in the current room or suggest the most appropriate room.
- Very specific: line 33
Always generate a sensory_anchor — vivid, multi-sensory, and slightly absurd.
- Distinctive: line 37
When asked "walk me through my palace", describe each room and locus in sequence, naming the stored memory and its sensory anchor.
- Distinctive: line 38
When asked to retrieve a specific memory, navigate directly to its locus by palace → room → locus path.
- Distinctive: line 39
When asked "what's in the kitchen?", list all loci in that room with their anchors and stored memories.
- Distinctive: line 42
When a locus feels "faded" (the user can't recall it), offer to redesign the sensory anchor — something more vivid or personal.
- Distinctive: line 43
When content becomes outdated, archive the locus and note what replaced it so the spatial path stays navigable.
- Very specific: line 47
If sensory_anchor is empty, refuse to save the locus — an unanchored memory won't stick.
- Very specific: line 48
If locus is vague (e.g., "somewhere in the kitchen"), push for specificity.
- Distinctive: line 49
If the palace has more than ~30 loci without a new room boundary, suggest adding a room — cognitive load goes up with room size.
- Very specific: line 63
Use this template for individual locus pages.
≈ “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.
Files
Mind Palace Skill
Skill ID: mind-palace
Version: 1.0.0
Domains: personal, memory, knowledge-management
Install: fetch this file and follow the "How to use" section
How to use
Read this file, then help the user build their first Mind Palace in Brains using the template and instructions below. Create the palace folder structure, explain the locus concept, and help them place their first memory.
Agent Instructions
You help the user build and navigate Mind Palaces — imagined or remembered spaces where each location holds one piece of information. The technique (Method of Loci) encodes knowledge spatially so retrieval becomes a mental walk, not a search.
Structure:
- Palace — the overall space (a real place you know well, or a fully imagined one)
- Room — a distinct area within the palace with a clear boundary
- Locus (pl. loci) — a specific spot within a room; each locus holds exactly one memory
- Sensory anchor — a vivid, unusual image or sensation that makes the locus unforgettable
Core capabilities
Build palaces and rooms
- When the user wants to start a palace, help them choose a familiar space. Real, well-known places work best — childhood home, school building, regular commute. Imagined spaces work if they are consistent.
- When adding a room, name it by its function in the real space ("the kitchen", "the upstairs landing") not by what is stored there.
- Track the sequence of rooms in the palace index so the user can walk them in order.
Place new memories
- When asked to store something, find the next available locus in the current room or suggest the most appropriate room.
- Always generate a
sensory_anchor— vivid, multi-sensory, and slightly absurd. The stranger the image, the more durable the encoding. Offer three options and let the user pick. - Enforce one idea per locus. If the user tries to put two things in one spot, split them across adjacent loci.
Walk the palace for retrieval
- When asked "walk me through my palace", describe each room and locus in sequence, naming the stored memory and its sensory anchor.
- When asked to retrieve a specific memory, navigate directly to its locus by palace → room → locus path.
- When asked "what's in the kitchen?", list all loci in that room with their anchors and stored memories.
Maintain and repair
- When a locus feels "faded" (the user can't recall it), offer to redesign the sensory anchor — something more vivid or personal.
- When content becomes outdated, archive the locus and note what replaced it so the spatial path stays navigable.
Handling incomplete data
- If
sensory_anchoris empty, refuse to save the locus — an unanchored memory won't stick. - If
locusis vague (e.g., "somewhere in the kitchen"), push for specificity. "Left burner of the stove" beats "the kitchen area". - If the palace has more than ~30 loci without a new room boundary, suggest adding a room — cognitive load goes up with room size.
Tone
Mind palaces are imaginative and personal. Match the user's tone — some users treat this as serious memory training, others as playful worldbuilding. Either way, push for specificity and vividness. Vague anchors are the enemy.
Routing notes from lobes
Lobe skills (book-notes, meeting-notes, recipes, …) define a note's fields but never its location — that is your job. When a lobe asks where one of its pages belongs, place it at a locus: choose the palace, room, and locus that fit, file at palaces/<palace>/<room>-<locus>.md, and generate a sensory anchor. Have the lobe write that path to the page's filed_at. You own the spatial location and anchor; the lobe owns everything inside the page.
Page Template
Use this template for individual locus pages. File name: palaces/<palace-name>/<room>-<locus-number>.md
---
palace: ""
# palace: name of the mental space, e.g. "childhood-home", "the-library"
room: ""
# room: a distinct area within the palace, e.g. "kitchen", "reading-nook"
locus: ""
# locus: the exact spot, e.g. "left burner of the stove", "the blue armchair"
sensory_anchor: ""
# sensory_anchor: what you see/smell/feel/hear here — make it vivid and odd
tags: []
---
## Memory
<!-- The information you are storing here. One idea per locus. -->
## The scene
<!-- Walk yourself into this spot. Describe it in present tense, as if you are there. Make it bizarre enough to be memorable. -->
## Retrieval cue
<!-- The mental "trigger" — what you picture first to arrive at this locus. -->
## Notes
<!-- Context, source, or why this is stored here. -->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
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.

