mind-palace

Query Mind Palace YAML entities for codebase subsystem knowledge.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/KohlJary/daedalus --skill mind-palace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mind-palace
Source: https://github.com/KohlJary/daedalus/tree/main/.claude-plugin/skills/mind-palace
Command: npx skills add https://github.com/KohlJary/daedalus --skill mind-palace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you explore and query subsystems of a codebase through the Mind Palace metaphor. It centralizes architectural knowledge (keepers, rooms, slugs) so you can understand how systems fit together and spot hazards before making changes.

Core Features & Use Cases

  • Read palace index: Inspect .mind-palace/palace.yaml to list entities.
  • Query an entity: Access .mind-palace/entities/<entityname>.yaml to learn HOW it works, WHY it's designed that way, and WATCH_OUT warnings.
  • Navigate by sub-palaces: Explore regional palaces (backend/admin/tui/mobile) to understand scope before refactoring.

Quick Start

Ask the AI to read palace.yaml and an entity's YAML, e.g., "What does MemoryKeeper know about semantic memory?" to surface architecture and potential hazards before modifying code.

Frequently Asked Questions about mind-palace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query codebase architecture and subsystem knowledge before making changes?

Mind Palace lets you query codebase architecture by reading entity YAML files that document HOW subsystems work, WHY they're designed that way, and WATCH_OUT hazards. Start with `.mind-palace/palace.yaml` to list entities, then access specific entity definitions to understand system interactions before refactoring.

What is the Mind Palace metaphor and how does it organize codebase knowledge?

Mind Palace is a metaphor-based system that centralizes architectural knowledge using keepers, rooms, and deterministic slugs. It structures codebase subsystems into navigable regions (backend, admin, tui, mobile) so you can explore scope and dependencies without reading scattered documentation.

Can I use Mind Palace to identify potential hazards before modifying code across my codebase?

Yes. Mind Palace surfaces WATCH_OUT warnings and architectural constraints in entity definitions, letting you spot cross-subsystem hazards and design decisions before making changes. Read palace index and relevant entity files to check impact across regions.

How do I navigate regional palaces to understand subsystem scope?

Mind Palace supports sub-palaces organized by region (backend, admin, tui, mobile). Access `.mind-palace/entities/` to explore region-specific entity definitions, understanding scope and boundaries before refactoring or integrating changes across subsystems.

What file format does Mind Palace use to store architectural knowledge?

Mind Palace stores architecture in YAML files: `palace.yaml` for the index listing all entities, and individual `.mind-palace/entities/<entityname>.yaml` files containing HOW, WHY, and WATCH_OUT documentation for each codebase subsystem.

Do I need existing architectural documentation to set up Mind Palace?

Mind Palace centralizes knowledge you already have or create. You populate `.mind-palace/palace.yaml` and entity files with your subsystem definitions, HOW-it-works details, design rationale, and hazard warnings—no external tool dependency required.

Related Skills