Agent skill
manage-localmemory
Local memory storage patterns, file coordination, and cleanup
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/manage-localmemory
SKILL.md
Memory Management Rules
Local Memory Storage
- Location:
${PROJECT_ROOT}/.claude/.localmemory/ - Purpose: Task progress and intermediate results
- Scope: Local only - NEVER commit to git
- Path Type: ALWAYS use absolute paths (never relative paths)
Folder Structure
Pattern: ${PROJECT_ROOT}/.claude/.localmemory/{action}-{module-identifier}/
CRITICAL: Always construct absolute paths using:
PROJECT_ROOT="$(git rev-parse --show-toplevel)"
MEMORY_PATH="${PROJECT_ROOT}/.claude/.localmemory/${action}-${moduleId}"
Where module-identifier is:
{vendor}-{module}for simple modules{vendor}-{suite}-{module}when suite exists
Examples (where PROJECT_ROOT is your project's absolute path):
${PROJECT_ROOT}/.claude/.localmemory/create-github-github/${PROJECT_ROOT}/.claude/.localmemory/update-amazon-aws-s3/${PROJECT_ROOT}/.claude/.localmemory/fix-gitlab-gitlab/
Phase Output Files
Standard naming in memory folders:
phase-01-discovery.json
phase-02-scaffolding.json
phase-03-api-spec.json
phase-04-type-generation.json
phase-05-implementation.json
phase-06-testing.json
phase-07-documentation.json
phase-08-build.json
phase-09-validation.json
_work/ # Working files
Context Passing
- Each phase reads previous phase output
- Each phase writes standardized output
- Use JSON format for structured data
- Include status and metadata
Important Notes
- Memory folders created by first running task
- No folder = work not started yet
- Clean up after workflow completion
- Never reference in production code
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?