Core Concepts

Promemo stores memory as Markdown inside .promemo/. That memory is divided into project-wide context, shared context, and feature-specific context.

Project Memory

Project-level memory lives in:

.promemo/project.md

Use it for durable context that applies across the repository, such as product goals, architecture principles, conventions, or high-level implementation notes.

Shared Memory

Shared memory lives under:

.promemo/shared/

Promemo initializes shared files such as:

.promemo/shared/architecture.md
.promemo/shared/coding-guidelines.md
.promemo/shared/notes.md

These files are useful for cross-feature context that should be loaded alongside feature-specific memory.

Feature Memory

Each feature gets its own folder:

.promemo/features/<feature>/

The canonical feature memory file is:

.promemo/features/<feature>/memory.md

Promemo also writes browsable generated views:

.promemo/features/<feature>/context.md
.promemo/features/<feature>/architecture.md
.promemo/features/<feature>/decisions.md
.promemo/features/<feature>/api.md
.promemo/features/<feature>/data-model.md
.promemo/features/<feature>/todos.md
.promemo/features/<feature>/prompts.md

Free-form human notes belong in:

.promemo/features/<feature>/notes.md

Promemo creates notes.md, but does not overwrite it.

Generated Regions

Promemo-owned Markdown is wrapped in generated-region markers:

<!-- promemo:generated:start -->
...
<!-- promemo:generated:end -->

Content outside those markers is preserved when Promemo rewrites generated memory files.

MemoryInput

MemoryInput is Promemo's structured memory contract. It can include:

• title
• summary
• current_state
• architecture
• decisions
• api
• data_model
• files
• todos
• open_questions
• future_work
• prompts

You can print the schema with:

promemo schema memory-input