home / skills / athola / claude-night-market / session-palace-builder

This skill helps you manage session-scoped memory palaces for complex projects, preserving context, tracking decisions, and organizing artifacts across

npx playbooks add skill athola/claude-night-market --skill session-palace-builder

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.5 KB
---
name: session-palace-builder
description: 'Consult this skill for session-scoped temporary knowledge structures.
  Use when working on complex multi-step projects, preserving context across interruptions,
  tracking session-specific state. Do not use when permanent knowledge structures
  needed - use memory-palace-architect. DO NOT use when: searching existing knowledge
  - use knowledge-locator.'
category: session-management
tags:
- session
- context
- project-memory
- conversation-state
- temporary-storage
dependencies:
- memory-palace-architect
scripts: []
usage_patterns:
- session-context
- project-tracking
- state-management
complexity: intermediate
estimated_tokens: 500
---
## Table of Contents

- [What It Is](#what-it-is)
- [Quick Start](#quick-start)
- [Mental Model](#mental-model)
- [When to Use](#when-to-use)
- [Session Palace Templates](#session-palace-templates)
- [Information Categories](#information-categories)
- [Core Workflow](#core-workflow)
- [Session Lifecycle](#session-lifecycle)
- [Detailed Resources](#detailed-resources)
- [Integration](#integration)


# Session Palace Builder

Construct temporary, session-specific memory palaces for extended conversations and complex projects. Preserves context across interruptions and enables structured information accumulation.

## What It Is

Session palaces are lightweight, temporary memory structures that:
- Preserve context for extended conversations
- Track decisions and their rationale
- Organize project artifacts spatially
- Enable context recovery after interruptions
- Support collaborative information gathering

## Quick Start

### Build Commands
\`\`\`bash
# Run build
make build

# Clean and rebuild
make clean && make build
\`\`\`

### Testing
\`\`\`bash
# Run tests
make test

# Run with verbose output
make test VERBOSE=1
\`\`\`

**Verification**: Run `make build && make test` to confirm build works.
## When To Use

- Extended conversations requiring context preservation
- Complex, multi-step projects with interrelated components
- Workflows requiring state management across interactions
- Collaborative sessions accumulating information over time
- Code review or debugging sessions with many findings

## When NOT To Use

- Permanent knowledge structures
  needed - use memory-palace-architect
- Searching existing knowledge
  - use knowledge-locator
- Permanent knowledge structures
  needed - use memory-palace-architect
- Searching existing knowledge
  - use knowledge-locator

## Session Palace Templates

| Template | Purpose | Key Areas |
|----------|---------|-----------|
| **Workshop** | Active development | Workbench, tools, materials |
| **Library** | Research and analysis | Stacks, reading room, archives |
| **Council Chamber** | Decision-making | Round table, evidence wall, vote board |
| **Observatory** | Exploration and discovery | Telescope, star charts, log book |
| **Forge** | Implementation tasks | Anvil, cooling rack, finished goods |

## Information Categories

Organize session content into these standard areas:

- **Conversations** - Dialogue threads and key exchanges
- **Decisions** - Choices made with rationale
- **Code** - Snippets and technical artifacts
- **Research** - Findings and references
- **Requirements** - Specifications and constraints
- **Progress** - Completed milestones
- **Issues** - Blockers and challenges
- **Next Steps** - Pending action items

## Core Workflow

1. **Analyze Context** - Assess session scope and complexity
2. **Design Palace** - Select template and layout
3. **Structure State** - Organize information spatially
4. **Build Navigation** - Create access shortcuts
5. **Test Integration** - Verify context preservation

## Session Lifecycle

```
Create → Populate → Navigate → Export/Archive
   ↑         ↓          ↓
   └─── Checkpoint ←────┘
```
**Verification:** Run the command with `--help` flag to verify availability.

## Detailed Resources

- **Template Details**: See `modules/templates.md`
- **State Management**: See `modules/templates.md`
- **Export Patterns**: See `modules/templates.md`

## Integration

- `memory-palace-architect` - Export important concepts to permanent palaces
- `knowledge-locator` - Search session content
- `digital-garden-cultivator` - Seed garden with session insights
## Troubleshooting

### Common Issues

**Command not found**
Ensure all dependencies are installed and in PATH

**Permission errors**
Check file permissions and run with appropriate privileges

**Unexpected behavior**
Enable verbose logging with `--verbose` flag

Overview

This skill constructs session-scoped temporary memory palaces to preserve context and state across interruptions during multi-step projects. It organizes decisions, artifacts, and progress into lightweight, navigable structures that support collaborative and extended workflows. Use it for transient project context that should not become permanent knowledge.

How this skill works

The skill inspects current conversation and project context, selects or builds a template palace (Workshop, Library, Forge, etc.), and places categorized items into spatial slots (Conversations, Decisions, Code, Issues). It maintains navigation shortcuts, checkpoints, and export hooks so context can be resumed, shared, or archived into a permanent memory palace when needed.

When to use it

  • Extended conversations requiring reliable context preservation
  • Complex, multi-step projects with interrelated components
  • Collaborative sessions that accumulate findings over time
  • Code review or debugging sessions with many findings to track
  • Workflows needing session-scoped state without creating permanent records

Best practices

  • Choose a template that matches the session goal (e.g., Workshop for dev, Library for research)
  • Keep entries concise and categorized: Conversations, Decisions, Code, Research, Issues, Next Steps
  • Create checkpoints at natural breaks to enable quick resume after interruptions
  • Use navigation shortcuts and a simple naming convention for artifacts
  • Export or archive only finalized concepts to a permanent memory palace (memory-palace-architect)

Example use cases

  • A multi-day refactor where decisions, code snippets, and blockers must be tracked across breaks
  • Collaborative debugging session where each finding and repro step is recorded and prioritized
  • Research sprint that collects references, notes, and hypotheses in a Library-style palace
  • Design workshop capturing proposals, votes, and rationale in a Council Chamber template
  • QA cycle where issues, test results, and next steps are organized and handed off

FAQ

When should I not use this skill?

Do not use it for permanent knowledge or for searching existing knowledge. Use memory-palace-architect for permanent structures and knowledge-locator for search tasks.

How do I recover session state after an interruption?

Use saved checkpoints and navigation shortcuts created during the session to resume from the last recorded location.

Can I export session content?

Yes. Export hooks let you archive selected items to permanent palaces or external formats; export only finalized concepts to avoid clutter.