create-memory-note

Atomic note creation skill that enforces all memory-rules before write_note(). Use this skill for EVERY new note creation to ensure quality standards. Read rules from memory-rules project: - search_notes(query="New Note Checklist", project="memory-rules") - search_notes(query="Relation Creation Rules", project="memory-rules") Search current project for duplicates using semantic search: - search_notes(query="topic keywords", project="target-project", search_type="semantic") If potential duplicate found, decide: update existing or create new Prepare title: Specific, searchable, follows templates Prepare observations: 3-5 with specific categories Prepare tags: 3-5 relevant, lowercase hyphenated Choose folder: Appropriate for content type If note_type is known, include it as a tag (e.g., "decision", "bug-report", "code-pattern") For EACH planned relation: 1. Search for target: search_notes(query="target title", project="current") 2. Verify target exists in search results 3. Verify target ≠ current note title (NO SELF-REFERENCE) 4. Verify target in same project (or use text format for cross-project) 5. Copy exact title from search results 6. Choose specific relation type (not generic relates_to) Before write_note(), verify: - [ ] Title is specific and unique - [ ] 3-5 observations with categories - [ ] 2-3+ relations, all verified - [ ] No self-referential relations - [ ] No cross-project WikiLinks - [ ] Tags are relevant and searchable - [ ] Folder is appropriate Execute write_note() with prepared content If a schema exists for this note type (e.g., design-decision, bug-report), set the frontmatter type field accordingly Verify creation: read_note() to confirm Check resolved vs unresolved relations in response After creating the note, assess: does this introduce a NEW topic area to the project? Indicators of new topic area: - First note in a new folder/category - Describes a completely new concept not covered by existing notes - Would be useful as an entry point for understanding the project If YES: read per-project index note, append new entry-point link using edit_note() If NO (most cases): no index change needed Index notes MUST use "documents" or "encompasses" relation types — NEVER "relates_to"

<rules_reference> memory-rules <anti_patterns>anti-patterns/Self-Referential Relations Anti-Pattern</anti_patterns> <anti_patterns>anti-patterns/Cross-Project WikiLinks Anti-Pattern</anti_patterns> <anti_patterns>anti-patterns/Generic Titles Anti-Pattern</anti_patterns> creating-notes/New Note Checklist creating-notes/Relation Creation Rules creating-notes/Title and Metadata Standards quality/Observation Standards <final_check>quality/Pre-Publish Checklist</final_check> Per-project index note — update only for new topic areas </rules_reference>

<critical_rules> NEVER create self-referential relations (target = current note) ALWAYS search and verify relation targets before adding Use text format "Title" (project) for cross-project references Use specific relation types: implements, requires, part_of, extends </critical_rules>