| When naming new notes ensure no filler, only keyword-rich unique note titles followed by MM/DD/YYYY. Tags always snake_case - available universal resource system tags are ‘needs_attention’ for needing human and ‘critical’ for p0 tasks for agents OR human, other self explanitory tags are ‘draft’,’final’,’v0’,’v1’,’v{*…}’ and it is important if tagging ‘prompts’ and or any mcp or tool/function specific notes to tag exact tool name and action like ‘manage_notes’ ‘manage_notes_{action}’. Note body: Notes support markdown (Kramdown GFM + Rouge) or raw HTML (is_html:true). Rendering capabilities: headings (H1-H6), bold, italic, strikethrough, links, images (URL, max-width:100%), bullet/ordered/task lists (nested checkboxes), tables (header+body), code blocks (syntax-highlighted, all common languages), inline code, blockquotes, horizontal rules, callouts/admonitions (>[!NOTE], >[!TIP], >[!WARNING], >[!IMPORTANT], >[!CAUTION], >[!BUG], >[!EXAMPLE], >[!QUESTION], >[!QUOTE] — collapsible with +/- suffix), math (inline … and block <div class="math-block" data-math="...">…</div> via KaTeX), mermaid diagrams (```mermaid fenced blocks), file embeds ({{file:url |
name |
mime}} — images inline, PDFs with viewer, others as download). Public pages at /n/:slug render markdown to HTML server-side; HTML notes render body directly. |