Results for “working-memory”

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Save information to persistent memory for cross-session recall. Stores preferences, conventions, decisions, and context.

Memory (acaf-memory)

Foundational C programming patterns covering type system, memory management, pointers, arrays, preprocessor, compilation, concurrency (pthreads, mutexes, atomics), serialization (binary, JSON, struct packing), and testing (Unity, CMocka, Check). Complete 8/8 pillar coverage. Use when writing C code, understanding manual memory management, working with system-level programming, or needing guidance on which specialized C skill to use. This is the entry point for C development.

Capture durable project memory from work, debates, debugging discoveries, learned conventions, deferred options, and session outcomes. Load when the user says remember this, save this learning, record what happened, update project memory, or preserve context for future agents.

Transforms lessons learned into domain-organized memory instructions (global or workspace). Syntax: `/remember [>domain [scope]] lesson clue` where scope is `global` (default), `user`, `workspace`, or `ws`.

Merges mature lessons from a domain memory file into its instruction file, preserving knowledge with minimal redundancy.

Memory System Management

clawhip × filesystem-offloaded memory

Use before starting any new work to check for existing knowledge. This skill provides a systematic search and retrieval process for finding relevant knowledge from memory systems (PARA, Gigabrain, OpenStinger, existing skills) before starting work, preventing redundant effort and leveraging prior learning.

Promote project-specific memories into strict, small global memory only when they are cross-project, stable, useful, safe, and worth the global context cost. Load when the user says make this global, remember across projects, save this globally, or promote this learning.

Sync durable project or session knowledge into the available memory systems so future sessions have accurate context. Use when meaningful work is complete and the user wants the result remembered.

Surface relevant project memory at session start or on demand. Trigger: session start, 'recall', 'remember', 'what do you know', 'context', /recall

Consolidates project memory across harness and .memory/ with theme clustering, practical-expiry prune, ground-truth verify, and an adversarial second pass. Use when the user runs /memory:consolidate, asks to tidy/dedupe/prune memory, or reports redundant or stale memories. Also covers active writing during work.

Persistent cross-session memory management. Enables agents to remember user preferences, project conventions, and past decisions across different sessions using a structured MEMORY.md index and topic files.

Memory (aeaf-memory)

Memory (aaaf-memory)

Iron Law

Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics.

Memory systems specialist for hierarchical memory, consolidation, and outcome-based learningUse when "memory system, memory hierarchy, memory consolidation, forgetting strategy, salience learning, outcome feedback, temporal memory levels, entity resolution, memory, zep, graphiti, mem0, letta, hierarchical, consolidation, salience, forgetting, ml-memory" mentioned.

Memory (adaf-memory)

Memory (abaf-memory)

Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:review or asks what has been learned and what should be promoted or pruned.

Delete, redact, or archive project and global memories when the user says forget this, delete memory, remove that preference, do not remember, redact sensitive information, or retire stale memory.

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.

Foundational Objective-C patterns covering classes, protocols, categories, memory management (ARC/retain-release), blocks, GCD, and Foundation framework. Use when writing Objective-C code, working with Cocoa/Cocoa Touch APIs, bridging to Swift, or needing guidance on Apple platform development patterns. This is the entry point for Objective-C development.