메뉴
Resume prior work by rebuilding context from the Basic Memory knowledge graph — pick up where you left off using memory:// URLs, recent activity, and search. Use when starting a session or when the user says 'continue with...', 'back to...', or 'where were we?'
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Orient Claude from Basic Memory before substantial repo work by reading active tasks, open decisions, recent checkpoints, and repo conventions. Use when resuming old work or when the user asks where things stand.
Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the plugin.
Show the Basic Memory plugin's current state for this project — active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable.
Save a deliberate Codex work checkpoint to Basic Memory with changed files, verification, decisions, blockers, and the next action.
Orient Codex from Basic Memory before substantial repo work by reading active tasks, decisions, recent Codex checkpoints, and repo conventions.
Set up Basic Memory for Codex at user or project level by mapping a Basic Memory project and seeding schemas.
| name | memory-continue |
| description | Resume prior work by rebuilding context from the Basic Memory knowledge graph — pick up where you left off using memory:// URLs, recent activity, and search. Use when starting a session or when the user says 'continue with...', 'back to...', or 'where were we?' |
Resume previous work by reconstructing context from the Basic Memory knowledge graph, so the assistant can pick up across sessions instead of starting cold.
If it's unclear, ask:
Known topic — use build_context. Navigate the graph from a starting point, following relations outward:
build_context(
url="memory://topic-or-note-name",
depth=2, # how many relation hops to follow
timeframe="7d", # bias toward recent changes
)
No clear starting point — use recent_activity. See what's changed and let it surface the thread:
recent_activity(timeframe="3d", depth=1)
Looking for something specific — use search_notes. Find candidate notes by keyword:
search_notes(query="async client refactor", page_size=10)
Once you've identified the relevant notes, read them in full:
read_note(identifier="note-title-or-permalink")
Summarize what you found, incrementally:
build_context and read_note both accept memory:// URLs, which address notes by permalink and support wildcards for gathering groups of notes.
memory://note-title # a single note by permalink
memory://folder/* # all notes in a folder
memory://specs/SPEC-24* # pattern / prefix match
memory://project/*/requirements # path wildcards
Use a specific note URL to anchor on one starting point; use a wildcard to pull in a whole folder or family of related notes at once.
build_context and recent_activity accept natural-language timeframes:
| Timeframe | Meaning |
|---|---|
"today" | Current day |
"yesterday" | Previous day |
"3d" or "3 days" | Last 3 days |
"1 week" or "7d" | Last week |
"2 weeks" | Last 2 weeks |
"1 month" | Last month |
# 1. Read the spec / project note
read_note(identifier="SPEC-24: Postgres Database Migration")
# 2. Pull in related context and recent changes via the graph
build_context(url="memory://SPEC-24*", timeframe="7d")
Then summarize: the goals, what's completed, what's pending, and any blockers or open decisions.
# 1. Check recent activity
recent_activity(timeframe="3d")
# 2. Read notes from the recent sessions it surfaces
read_note(identifier="relevant-note")
Then list the modified notes with brief descriptions and ask which thread to dive into.
# 1. Find the topic
search_notes(query="topic keywords")
# 2. Build context from the best match, following its relations
build_context(url="memory://found-note-permalink", depth=2)
Then present the full picture — the note plus its connected context.
Project names are user-specific. To discover what's available before scoping a search or memory:// URL:
list_memory_projects()
In multi-project setups, prefix a memory:// URL with the project name (e.g. memory://research/papers/crdt) to scope it.
recent_activity or a wildcard build_context, then drill into specific notes.build_context with depth surfaces context you wouldn't find by reading one note.list_memory_projects.