notes

name	notes
triggers	["note","save","write","markdown"]
description	Markdown file conventions and note-saving procedures

File format

• Always save notes as .md (markdown)
• Filename: descriptive sentence with spaces (e.g. Meeting notes from Thursday.md), not slugified or kebab-case
• Use YAML frontmatter with at least a created date field
• If the note has non-obvious read/write quirks worth pinning (ordering, structure, things to avoid), set an agents: field — a single 1–3 sentence string of per-file instructions, written as a quoted YAML string (e.g. agents: "Append new entries at the top."). See the "Markdown frontmatter" section of the system prompt for the full convention.

Markdown conventions

• No escaping of special characters in markdown body text
• Use standard markdown links: [label](<path with spaces>)
• Never use %20 encoding in link paths
• Let markdown render handle special characters naturally

Save location

The notes/ folder under your bot dir is where {BOT_NAME} writes new notes and transcriptions. This is distinct from broader shared folders the user may have — those are for reading, this is the write destination.

Save to whichever of these applies (first match wins):

1. A path the user specifies in their message
2. A specific path mentioned in user memory
3. The default {BOT_DIR}/notes/ folder

Don't ask where to save unless the destination is ambiguous.