Delegate independent tasks to specialized agents working concurrently with isolated context.
🏛️ Memory Palace Skill
memory-palace
Spatial organization of knowledge in navigable directories
SKILL.md
Full skill instructions
🏛️ Memory Palace Skill
"The filesystem is the mind. Directories are rooms. Files are objects."
The ancient method of loci, adapted for LLMs navigating filesystems.
The Technique
Place knowledge in locations. Navigate to remember.
Each room contains:
- Objects (files) — artifacts to examine
- Exits (links) — doors to other rooms
- Atmosphere — the room's essence
This IS the Room Skill
Memory Palace and Room are deeply connected:
| Memory Palace | Room Skill |
|---|---|
| Location | Directory |
| Object | File |
| Traversal | Enter/Exit |
| Placement | Create file |
| Recall | Navigate to |
Memory Palace = Room + spatial mnemonic intent
Palace Structure
palace/
├── ENTRY.md # Front door (README)
├── MAP.yml # Navigation overview
│
├── concepts/ # Wing: Ideas
│ ├── ROOM.md
│ ├── yaml-jazz/
│ └── play-learn-lift/
│
├── characters/ # Wing: Personas
│ ├── ROOM.md
│ ├── gardener/
│ └── archivist/
│
└── skills/ # Wing: Capabilities
├── ROOM.md
└── ...
Placing Knowledge
To remember something:
- Choose a room — where does this belong?
- Create a file — the object to place
- Link it — connect to related objects
- Walk there — navigate to reinforce
# palace/concepts/yaml-jazz/ROOM.yml
room:
name: "YAML Jazz Chamber"
contains:
- "jazz-principles.md" # Core ideas
- "examples/" # Sub-room of examples
exits:
parent: "../"
related: "../play-learn-lift/"
atmosphere: "improvisational, semantic"
Core Files
ENTRY.md
The front door to your palace:
# Palace Name
## Welcome
What this palace contains and why.
## Quick Navigation
- [Room A](room-a/ROOM.md) - Description
- [Room B](room-b/ROOM.md) - Description
## Recent Activity
- Added X to Room A
- Created new Room C
MAP.yml
Navigation structure:
palace:
name: "Research Palace"
created: "2025-12-30"
rooms:
- name: "foundations"
path: "foundations/"
description: "Core concepts"
connects_to: ["applications", "history"]
- name: "applications"
path: "applications/"
description: "Practical uses"
connects_to: ["foundations", "examples"]
landmarks:
- name: "The Big Question"
location: "foundations/core-question.md"
importance: "Start here"
ROOM.md (in each room)
# Room Name
## What's Here
Description of this room's contents.
## Artifacts
- [artifact-1.md](artifact-1.md) - Description
## Doors
- ← Back to [Entry](../ENTRY.md)
- → Forward to [Next Room](../next-room/ROOM.md)
## Notes
Observations, questions, TODOs for this room.
Navigation Commands
| Intent | Action |
|---|---|
| "Enter the palace" | Read ENTRY.md |
| "Look around" | ls current directory |
| "Go to room X" | cd to room, read ROOM.md |
| "Examine artifact" | Read the file |
| "Leave a note" | Create/update .meta.yml |
| "Create new room" | mkdir + create ROOM.md |
| "Check the map" | Read MAP.yml |
| "Where am I?" | Note current path |
Lifecycle
Create
- mkdir palace root
- create ENTRY.md
- create MAP.yml
- create initial rooms
Expand
- create new room directory
- add ROOM.md
- update MAP.yml
- link from related rooms
Maintain
- update MAP.yml periodically
- add cross-references
- archive stale rooms
- create summaries
Archive
- move to attic/
- note in MAP.yml
- update links
Tips
- Start small — Begin with 3-5 rooms, expand as needed
- Name meaningfully — Directory names are addresses
- Link generously — Cross-references aid recall
- Leave breadcrumbs — Update .meta.yml as you explore
- Maintain the map — MAP.yml is your table of contents
- Archive, don't delete — Move stale rooms to attic/
Integration
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
