Memory hygiene

Store durable, useful facts through the active host's supported memory system.

Discover the storage contract

Inspect available memory tools, host instructions, and existing project conventions. Determine scope, storage location, entry format, retrieval behavior, and whether saving is authorized.

Do not replace a native backend with files merely because this skill describes a file pattern. Do not assume MEMORY.md is automatically loaded or that a particular taxonomy is required.

Select content

• Keep durable preferences, corrections, ongoing project decisions, and stable reference pointers.
• Distinguish user facts from inferred preferences.
• Record the source and relevant scope; preserve uncertainty where present.
• Store the reason and application trigger for behavioral feedback.
• Keep transient run state in a handoff or task record.

Use host-supported types. Where a file-based convention already uses user, feedback, project, and reference categories, preserve those categories.