manage-localmemory

Stores and retrieves JSON phase outputs in a hidden .localmemory directory without git-tracking.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill manage-localmemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-localmemory
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/manage-localmemory
Command: npx skills add https://github.com/zerobias-org/module --skill manage-localmemory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local memory management is essential for coordinating task progress, intermediate results, and phase outputs within a project, without leaking state into version control.

Core Features & Use Cases

  • Local, isolated storage for task progress and intermediate results under ${PROJECT_ROOT}/.claude/.localmemory/ with absolute paths enforced.
  • Structured phase output files (phase-01-..., phase-02-... etc.) and a dedicated _work directory to hold working files.
  • Use cases include coordinating multi-phase workflows, caching results between steps, and cleaning up temporary data after workflow completion.

Quick Start

Store the first phase results in ${PROJECT_ROOT}/.claude/.localmemory/ and verify the presence of phase-01-discovery.json.

Frequently Asked Questions about manage-localmemory

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

FAQPage Schema
How do I store intermediate task results locally without committing them to git?

You can store intermediate task results in a dedicated hidden local memory store under the project root, keeping non-committal phase outputs isolated from version control while maintaining structured JSON data exchange.

What is the best way to track deterministic phase outputs across multi-phase workflows?

Deterministic phase outputs are tracked using structured JSON files named sequentially by phase within a hidden local memory store, providing isolated file coordination for multi-phase project workflows.

How do I cache intermediate results between workflow steps in a local memory store?

Caching intermediate results between workflow steps is handled by writing JSON-formatted data to structured phase files within a dedicated hidden memory store, enforcing absolute paths for reliable file coordination and task tracking.

Does local memory management enforce absolute paths for JSON-formatted data exchange?

Yes, local memory management enforces absolute paths for all file coordination operations, ensuring deterministic access to JSON-formatted phase outputs stored within the hidden memory store directory.

Can I clean up temporary data after workflow completion without affecting tracked files?

Yes, temporary data cleanup is fully supported after workflow completion because the local memory store operates entirely outside git-tracking, safely removing intermediate phase outputs and working files without affecting version control.

When should I use a local memory store instead of version control for task tracking?

A local memory store should be used for non-committal, in-process coordination across phases and tasks, specifically when caching intermediate results and deterministic phase outputs without polluting version control with temporary working files.