PMC

View saved version →

---
name: curate-project-memory
description: Give Codex lasting project context in a local Obsidian-compatible Markdown vault. Use when a user asks PMC to set up or connect the project's Obsidian vault, scan or explain a codebase, create a Project Home, remember a decision, constraint, discovery, procedure, debugging lesson, or current state, recall what Codex already knows, prepare a handoff, check whether notes are stale or contradictory, relate code to knowledge, keep something session-only, export or share reviewed context, or resume work from existing project notes.
---

# Curate Project Memory

Use conversation as the interface. Do not ask the user to run commands or edit configuration manually. Use Codex's normal file tools and request narrowly scoped filesystem permission when needed.

## First-run experience

When the user invokes PMC and no project registration exists for the current repository, lead with a concise guided setup instead of describing the architecture:

1. Explain in one sentence: "PMC gives Codex lasting project context in an Obsidian vault you control."
2. Ask whether to create a new vault or connect an existing Obsidian vault. Ask only this one question first.
3. After that choice, ask for or confirm the vault path, infer the current repository, and propose a readable project name.
4. Complete the vault setup and project registration conversationally. Do not require the user to know commands, markers, folder layouts, or configuration formats.
5. Create useful initial notes rather than empty shells whenever the repository can be inspected safely.
6. At completion, state where the vault and project notes live, explain how to open the vault in Obsidian, and offer to scan the repository now.
7. End with these examples: "@PMC remember this", "@PMC what do we already know about authentication?", and "@PMC wrap up this task".

Do not overwhelm a first-time user with advanced features. Introduce context packs, health checks, exports, team review, and the companion only when relevant.

Read `references/project-profiles.md` when choosing registration defaults.

Read `references/local-similarity.md` before building or querying the optional machine-local similarity index.

Read `references/storage-and-portability.md` for setup or project registration. Read `references/automatic-orientation.md` when the user wants the vault added as a project source or wants future chats to load project notes without a prompt. Read `references/durable-note-policy.md` before promoting, changing, or removing knowledge. Read `references/note-structure.md` when creating notes. Read `references/context-packs.md` when orienting or resuming work. Read `references/knowledge-health.md` before auditing a vault. Read `references/code-traceability.md` when relating notes to source files. Read `references/branch-awareness.md` before promoting knowledge discovered on a branch or worktree. Read `references/drift-detection.md` before creating or running verification checks. Read `references/coverage.md` before assessing documentation coverage. Read `references/team-collaboration.md` before configuring shared-vault ownership or reviews. Read `references/exports.md` before creating a portable brief or audit artifact. Read `references/obsidian-companion.md` when installing, configuring, or responding to review actions from the optional Obsidian companion.

## Boundaries

- Operate only on local paths that the user selects or places in scope.
- Do not upload, transmit, or add telemetry.
- Do not request or capture complete raw chat transcripts.
- Store an optional concise session summary only when the user asks to wrap up or enables summaries.
- Exclude secrets, credentials, private keys, authentication cookies, and unnecessarily sensitive data.
- Treat the vault as curated knowledge, not a chat archive.
- Never contradict, delete, or supersede durable knowledge silently.
- Do not require Obsidian community plugins.
- If local filesystem access is 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 46 — file references are metadata, not package contents.