/remember & /recall

Two paired skills for working memory: /remember stores notes, /recall finds them and searches the full wiki in the same query.

---

/remember#

Store a quick note in working memory.

Trigger phrases#

/remember, /rem, remember that, note that, save this for later, keep in mind, don't forget.

Do NOT use for: saving session state (use /state-save) or writing wiki pages directly.

What it does#

1. Extracts the note text and identifies an optional category:

Category	Triggered by
design	character, ability, weapon, balance, game mode, level
dev	code, class, function, module, build, compile
decision	decided, decision, chose, agreed, going with
bug	bug, broken, wrong, fails, crash, error
todo	todo, need to, should, must, remember to

2. Checks whether the note should go to the wiki instead. If the note is a factual statement about a character or system, or a design decision, /remember suggests wiki placement. You can override and store it as a note anyway.

3. Appends to Docs/_working/notes/YYYY-MM.md (monthly file):

- 2026-03-21 14:30 [design] Shield cap is 100. Decided to prevent stacking abuse (see Design/Characters/Sentinel.md)

4. If the note mentions a known entity (character name, class name, system name), adds a cross-reference pointer to the nearest wiki page.

When to use /remember vs the wiki#

Use /remember for: temporary observations, WIP notes, "remember for later", things you are not sure about yet.

Use the wiki (Docs/Design/ or Docs/Dev/) for: confirmed facts about characters and systems, finalized design decisions, architecture notes that should persist across sessions.

---

/recall#

Search across all memory layers and return results with source attribution.

Trigger phrases#

/recall, recall, what do we know about, find in memory, search wiki, look up, what did we decide about.

Do NOT use for: searching source code (use the explorer agent), or searching the web.

What it searches#

Searches in priority order:

1. Design wiki: Docs/Design/index.md then matching pages
2. Dev wiki: Docs/Dev/index.md then matching pages
3. Working notes: Docs/_working/notes/ monthly files
4. Decisions: Docs/Decisions/ (if populated)

/recall does NOT search session artifacts (Docs/_working/sessions/). Those are ephemeral work from past sessions that may reference reverted or abandoned code. For "what was I working on" queries, use /state-load instead.

Output format#

## Results for "shield bash"

### Design Wiki
- Design/Characters/Sentinel.md: "Shield Bash ability, 50 damage, 8s cooldown..."

### Dev Wiki
- Dev/Systems/Combat/overview.md: "GA_ShieldBash inherits from CDGameplayAbility..."

### Working Notes
- 2026-02-15: "Shield VFX is placeholder, needs particle rework"

### Decisions
- (none found)

Each result includes the source file path, a relevant excerpt (1–3 lines), and the Last Updated date if available.

No results#

If nothing is found across any layer, /recall suggests next steps:

No results found for 'shield bash'. Try:
- /map-design to populate the Design wiki from Blueprints
- /map-codebase to populate the Dev wiki from source code
- /remember to store what you know about this topic