create-new-memory-project

Atomic skill for creating new Basic Memory projects with full index registration. Enforces creation criteria, creates per-project index note, and registers in global PROJECT_DIRECTORY.

<creation_criteria> <create_when> Work spans 10+ notes on a distinct, bounded domain The domain has its own codebase/repository Notes would create noise in existing projects' search results </create_when> <reject_when> Topic fits within an existing project's scope — add notes there instead Temporary investigation — use a folder in the relevant project Fewer than ~5 notes expected — not worth the overhead Cross-cutting concern — belongs in development-practices or infrastructure Truly cross-cutting with no domain — use main </reject_when> </creation_criteria>

Review creation vs rejection criteria against the proposed project Call list_memory_projects() to check for existing project overlap Search existing projects for related content that might already cover this domain If criteria not met, recommend alternative (existing project, folder, or main) Use cross-project-search skill to identify related projects Note related projects for the per-project index (use text format, not WikiLinks) Call create_memory_project(name="project-name") Verify creation with list_memory_projects() Write per-project index note using the template below Use write_note(title="[Project Name] Index", folder="", tags=["index", "landing-page"], project="new-project") Include purpose, initial entry-point notes (if any exist), and related projects Read current PROJECT_DIRECTORY from main project: - read_note(identifier="project-directory", project="main") Add new entry following the global index entry template Use edit_note() to append the new project entry to PROJECT_DIRECTORY Update basic_memory_guide.md project list if accessible Add new project with purpose and when_to_use

<per_project_index_template> Minimal landing-page note, ~20-30 lines. Created in the root folder of the new project.

[Project Name] Index

Purpose

[1-2 sentences describing what this project covers]

Key Notes

• [[Key Note Title 1]] — brief description
• [[Key Note Title 2]] — brief description [3-5 entry points maximum, added as notes are created]

Related Projects

• "Related Note Title" (other-project) — how it relates [Text format, NOT WikiLinks — WikiLinks don't cross project boundaries] </per_project_index_template>

<global_index_entry_template> Entry format for PROJECT_DIRECTORY in main project

project-name

Purpose: One-line description of what this project covers When to use: Brief trigger criteria for when to add notes here </global_index_entry_template>

<index_update_principle> Index updates are the exception, not the rule. Only structural changes (new topic areas, removed entry points, consolidation of key notes) warrant an update. Most note operations do not touch the index. </index_update_principle>

<critical_rules> ALWAYS validate against creation/rejection criteria before creating ALWAYS create per-project index note immediately after project creation ALWAYS register in global PROJECT_DIRECTORY in main Use TEXT format for cross-project references in per-project index (not WikiLinks) Keep per-project index minimal: purpose + 3-5 entry points + related projects </critical_rules>

<rules_reference> memory-rules <new_note>creating-notes/New Note Checklist</new_note> creating-notes/Relation Creation Rules <cross_project>anti-patterns/Cross-Project WikiLinks Anti-Pattern</cross_project> Per-project index note and global PROJECT_DIRECTORY </rules_reference>