Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
The English summary is being prepared. Showing the original description.
Builds session-scoped temporary memory palaces for extended conversations. Use when tracking state across interruptions in a multi-step project.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Construct temporary, session-specific memory palaces for extended conversations and complex projects. Preserves context across interruptions and enables structured information accumulation.
Session palaces are lightweight, temporary memory structures that:
```bash
make build
make clean && make build ```
```bash
make test
make test VERBOSE=1 ```
Verification: Run make test to confirm the plugin gate passes.
| 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 |
Organize session content into these standard areas:
Create → Populate → Navigate → Export/Archive
↑ ↓ ↓
└─── Checkpoint ←────┘
Verification: Run the command with --help flag to verify availability.
A session palace decays silently: each Populate step can add
ambiguity that only surfaces at Export, when it is too late to
recover the lost state. MMPO (arXiv:2605.30159, Section 3) frames
this as a case for sub-trajectory dense rewards: check intermediate
quality at each transition, not just the final outcome.
At every Checkpoint arrow in the lifecycle above (and before any
Export/Archive), run the dual-probe gate against the current
palace state:
Skill(memory-palace:memory-clarity-probe)
The probe returns a Clarity Assessment with progress/gap verdicts
and a Recommendation:
| Recommendation | Action at the checkpoint |
|---|---|
| Proceed | Palace state is clear; continue the session |
| Expand memory | Add the gap probe's open items to the palace before continuing |
| Regenerate | Flag the session as ambiguous: the progress probe hedges, so reconstruct the current-state room before more work lands on it |
Flagging at the checkpoint, not at export, is the point: an ambiguous palace caught early costs one room rebuild; caught at export it costs the session.
When memory-clarity-probe is not installed, ask the two anchor
questions inline (progress: what is done and what state is the task
in; gap: what concrete items remain) and apply the same table.
modules/templates.mdmodules/templates.mdmodules/templates.mdmemory-palace-architect - Export important concepts to permanent palacesknowledge-locator - Search session contentdigital-garden-cultivator - Seed garden with session insightsmemory-clarity-probe - Dual-probe clarity gate at session checkpointsCheckpoint transition
and before Export/Archive, not only at the endExpand memory or Regenerate is acted
on (gap items added or current-state room rebuilt) before more work
lands, and the ambiguous session is flaggedmemory-palace-architectNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
The English summary is being prepared. Showing the original description.
Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.
The English summary is being prepared. Showing the original description.
Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.
The English summary is being prepared. Showing the original description.
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
The English summary is being prepared. Showing the original description.
Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.
The English summary is being prepared. Showing the original description.
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
The English summary is being prepared. Showing the original description.