Memory Guidance FAQs

Question 1

How is memory hygiene maintained?

Accepted Answer

The skill encourages periodic reviews to remove stale entries, consolidate duplicates, and promote significant decisions or conventions to formal documentation.

Question 2

How does memory differ from documentation in this skill?

Accepted Answer

Memory is intended for concise facts, developer preferences, and short-lived session context, while documentation is reserved for structured, long-form knowledge meant for team-wide reference and versioning.

Question 3

Can I use this skill to track bug investigations?

Accepted Answer

Yes, the skill includes a specific 'bugs' category designed to capture reproduction steps and root cause observations before they are promoted to formal issue trackers.

Question 4

How does the session workflow ensure continuity?

Accepted Answer

It follows a three-phase pattern: loading relevant context at the start of a session, capturing real-time updates during work, and saving a state summary at the end to brief the next session.

Question 5

What are the required tags for memory entries?

Accepted Answer

Every entry must include at least one module tag (e.g., api, ui) and at least one topic tag (e.g., database, testing) to enable effective filtering and retrieval.

Memory Guidance

Key Features

Use Cases

Memory Guidance

Key Features

Use Cases