菜单
Use proactively before answering when a task involves memory, "last time", "remember", prior decisions, user preferences, project history, source material, continuity/resume, grounded synthesis, contradiction checks, corpus import, durable writeback, or post-import dreaming through MOOTx01.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when an agent needs to compute a substrate hot-path primitive — SimHash, Hamming distance, OR-reduce, bitwise combinators, Fingerprint256 construction, HammingNN top-K nearest neighbors, BitField bitmap extraction, or a SHA-256 hash. These are byte-identical Swift+Rust implementations behind a conformance-gated CRC. Trigger this skill whenever an agent is about to hand-write any of those operations, or use any bit operation on a Fingerprint256. (The AuditGate write gate lives in SubstrateLib and HLCGenerator in SubstrateTypes — see their skills.) The skill redirects to the existing implementation and prevents re-invention drift the conformance harness would catch in CI.
Use this skill when an agent needs cold-path or dreaming-driven algorithms — matrix decay, moment summary OR-reduce, Bradley-Terry online weight update, anomaly z-score, information theory (entropy / MI / KL), temporal compression rollups, partial-state recall scoring, FFT for rhythm analysis, NMF factorization, eigenvalue centrality (keystone scoring), audit-log fold for state projection or as-of reads, tier-contribution federation aggregate, or pairing handshake to mint shared hyperplane seeds. All 15 are conformance-gated Swift+Rust byte-identical. Trigger this skill any time an agent is about to write one of those, run a recall query that needs as-of state, compute a population-stat update, or anything dreaming-daemon-shaped. Redirects to the existing implementation.
Use this skill when working with substrate row shape — declaring, serializing, or holding a row without computing on it. Covers Fingerprint256 (the 256-bit four-block container), HLC (hybrid logical clock value), Row / RowLite, LatticeAnchor, AuditEvent (struct shape), MatrixF/C/O/T (storage containers), layout constants (BlockMask, RowBitmaps, BitVector216), TimeRange, and substrate enums (MutationKind, PairingScope, GeneratedByClass, NounType, RowStateValue). Trigger this whenever an agent is about to declare a substrate struct field, define a CloudKit record, write a wire-format encoder, or stub out an audit event. Do NOT trigger for algorithms — those belong to SubstrateKernel or SubstrateML.
Building product features that USE EngramLib (Swift or Rust). Trigger when product code needs similarity, nearest-neighbor, radius search, or engram aggregation. Trigger on phrases including "EngramLib", "Engram", "find nearest", "Hamming similarity in app code", "recall similar", "build a feature on the substrate", "EngramLib.Session", "engram_kit". Do NOT trigger on kernel implementation, decision records, or substrate engineering maintenance — that is the substrate-engineering skill.
Use proactively before answering when a task involves memory, "last time", "remember", prior decisions, user preferences, project history, source material, continuity/resume, grounded synthesis, contradiction checks, corpus import, durable writeback, or post-import dreaming through MOOTx01.
Use proactively before answering when a task involves memory, "last time", "remember", prior decisions, user preferences, project history, source material, continuity/resume, grounded synthesis, contradiction checks, corpus import, durable writeback, or post-import dreaming through MOOTx01.
| name | mootx01-memory |
| description | Use proactively before answering when a task involves memory, "last time", "remember", prior decisions, user preferences, project history, source material, continuity/resume, grounded synthesis, contradiction checks, corpus import, durable writeback, or post-import dreaming through MOOTx01. |
Use MOOTx01 as an active memory and reasoning layer, not as a passive wiki.
Before answering any request that may depend on prior context, user preferences, project history, past decisions, continuity, or remembered source material, query MOOTx01 first.
After durable decisions, corrections, preferences, milestones, or useful project facts, write them back with the appropriate MOOTx01 tool.
If MOOTx01 tools are expected but unavailable, say so plainly. Never imply recall happened unless you actually queried it.
Orient:
moot_estate_pingmoot_estate_statusmoot_read_journal when continuity mattersmoot_estate_map when structure mattersRecall:
moot_memory_search for broad recall.moot_recall_precise for exact facts, paths, versions, names, numbers, and near-duplicates.moot_recall_shaped for associative, conceptual, or other fusion-steered recall.moot_recall_distilled for compact factoid answers from the distilled tier.moot_fact_search for structured facts.Analyze:
moot_list_lenses to discover available cognition tools.moot_lens_* tools for graph, theme, drift, contradiction, trust, cue, prediction, temporal, and information-theoretic analysis.moot_synthesize for grounded summaries.Write back:
moot_file_memory for durable observations and decisions.moot_file_fact for stable triples.moot_link_memories for durable relationships.moot_confirm_memory, moot_update_memory, moot_withdraw_memory, or moot_retire_fact for trust and correction.moot_write_journal for session continuity.Dream:
moot_reindex after batch import to populate semantic indexes.moot_dream after bulk import, major filing, or substantial memory growth.moot_consolidate periodically to populate the distilled factoid tier.Separate what MOOTx01 recalled, what MOOTx01 synthesized, and what you infer. If recall is thin or unavailable, say so plainly.