# Notes — Naming, Tagging &amp; Formatting Conventions

Published: 2026-04-01
Updated: 2026-04-01
Source: https://docs.oppy.pro/n/notes-naming-tagging-formatting-conventions
Account: Oppy Inc

---

# Notes — Naming, Tagging &amp; Formatting

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 &#39;needs_attention&#39; for needing human and &#39;critical&#39; for p0 tasks for agents OR human, other self explanitory tags are &#39;draft&#39;,&#39;final&#39;,&#39;v0&#39;,&#39;v1&#39;,&#39;v{*...}&#39; and it is important if tagging &#39;prompts&#39; and or any mcp or tool/function specific notes to tag exact tool name and action like &#39;manage_notes&#39; &#39;manage_notes_{action}&#39;. 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 (&gt;[!NOTE], &gt;[!TIP], &gt;[!WARNING], &gt;[!IMPORTANT], &gt;[!CAUTION], &gt;[!BUG], &gt;[!EXAMPLE], &gt;[!QUESTION], &gt;[!QUOTE] — collapsible with +/- suffix), math (inline $...$ and block $$...$$ 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.