amw-memory-write

Write symptom-indexed markdown memory notes into scoped local, project, or user memory directories.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-memory-write-emasoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amw-memory-write
Source: https://github.com/Emasoft/ai-maestro-webdesign/tree/main/skills/amw-memory-write
Command: npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-memory-write-emasoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won lessons, user corrections, and project gotchas are lost between sessions, forcing future work to re-solve the same non-obvious problems. This Skill captures each durable fact as a single markdown memory note that can be recalled later by its symptom. ## Core Features & Use Cases - Symptom-indexed notes: Writes one fact per note with the description field indexed by the question or error text a future session will search for, while the answer lives in the body. - Scope routing: Routes each note to LOCAL (machine-specific, never pushed), PROJECT (git-tracked under .claude/, no secrets), or USER (cross-project) memory directories based on the content of the fact. - Correction protocol: Demotes superseded facts into dated footnote lessons under a mandatory Notes and lessons learned section instead of silently deleting them, and updates MEMORY.md with a one-line index pointer. - Use Case: After discovering that OAuth credentials live in the macOS keychain during a failed login rotation, capture a note whose description reads like the symptom ("rotator failed, had to log in manually") so the next session finds it instantly. ## Quick Start Save a memory note about the login failure we just debugged so a future session can find it by the symptom.

Frequently Asked Questions about amw-memory-write

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

FAQPage Schema
How do I save a lesson so a future session can find it?▼

Write one markdown note per fact with the description field phrased as the symptom or question a future session will have, and put the actual answer in the note body. Then add a one-line pointer to MEMORY.md in the same memory directory.

What is the difference between LOCAL, PROJECT, and USER memory scope?▼

LOCAL holds machine-specific data like paths, usernames, and secrets and is never pushed. PROJECT holds shared knowledge tracked in the repo under .claude/ with no sensitive data. USER holds cross-project facts about the user in a fixed plugin data directory.

Should I recall existing memory before writing a new note?▼

Yes, always run the recall half first to check whether a matching note already exists. Updating an existing note avoids duplicates and keeps the memory index accurate.

What should I do when a saved memory turns out to be wrong?▼

Rewrite the body with the correct current fact and move the old claim into a dated footnote lesson under the Notes and lessons learned section, including why it was wrong. Never silently delete superseded facts.

When should I not write a memory note?▼

Do not record anything the repository already captures, such as code structure, git history, or CLAUDE.md content. Reserve notes for non-obvious problems, user corrections, and project constraints not derivable from the code.