@creator-notes/cli 0.2.3 → 0.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@creator-notes/cli",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "CLI for CreatorNotes — create notes, build canvases, search knowledge from the terminal",
   "type": "module",
   "bin": {

package/skills/cn/SKILL.md

@@ -196,6 +196,7 @@ cn config set-server <url>
   ```
 - Only use inline `--markdown "..."` for very short, single-line content.
 - The server converts markdown to TipTap JSON automatically.
+- **Always start markdown content with a `# h1` heading.** This becomes the note title. Follow proper markdown structure: `## h2` for major sections, `### h3` for subsections. Well-structured heading hierarchy is expected for all notes.
 - **Relationship mentions in markdown**: Use `[NOTE-123](relationship:references)` or `[NOTE-123: Title](relationship:references)` syntax — plain text "NOTE-123" does NOT create clickable mentions.
 - Supported relationship types: `depends-on`, `blocks`, `related-to`, `derived-from`, `references`, `extends`, `implements`, `invalidates`, `duplicates`
 - Simple mention shorthand: `[NOTE-123]` or `[NOTE-123: Title]` (defaults to "references")
@@ -236,6 +237,11 @@ Use `--size` to control text node font size (default: `heading`):
 | `heading` (default) | Section headers, zone titles, canvas labels |
 | `paragraph` | Descriptions, annotations, supporting context |
 
+#### Text Node Style
+
+- **Never use ALL CAPS** for text node content. Use title case instead (e.g., "Key Tensions" not "KEY TENSIONS").
+- Keep text labels concise — they are structural signposts, not paragraphs.
+
 #### Positioning Algorithm
 
 1. **Build the graph** — list all notes and their relationships.