Create a new note for: $ARGUMENTS

Instructions

  1. Run this now to see the current content structure, then pick the right destination:
find content -mindepth 1 -maxdepth 2 -type d ! -path "*/\.*" ! -path "*/private*" | sort | while read d; do title=$(grep "^title:" "$d/index.md" 2>/dev/null | head -1 | sed 's/title: //'); echo "$d${title:+  ($title)}"; done
  1. Choose the destination directory based on the note subject.

  2. Determine the register:

    • PTGAE (default for all published content): follow the style guide at content/writing/texts/style-guide.md.
    • emsenn’s voice (babbles, letters, personal writing): follow the voice notes at content/personal/writing/style/voice-notes.md.
  3. Determine the content type from the destination directory and check the style guide for its structural template:

    • terms/ → opening sentence + elaboration + related terms. Cite who introduced the term.
    • concepts/ → organized under clear headings, cite sources per section.
    • texts/ → thesis + evidence + conclusion. Follow discipline-appropriate citation conventions.
    • disciplines/ → opening + methods + key texts + key thinkers + subdirectory overview.
    • schools/ → opening + methods/approach + key texts + key thinkers + relationship to vault + critiques.
    • curricula/ → use the write-lesson skill instead.
    • encyclopedia/ → factual, concise, every claim cited.
    • personal/writing/babbles/ → relaxed structure, emsenn’s natural voice.
  4. If the destination subdirectory doesn’t exist yet, create it with an index.md first (no loose .md files at discipline roots).

  5. Derive a kebab-case filename. For babbles, match the date-time format of existing files (e.g., 2026-03-03-1400h.md).

  6. Write the file with frontmatter:

    ---
    title: "Note Title"
    date-created: 2026-03-03T00:00:00
    tags:
      - [relevant tags]
    ---
  7. Write the body following the content-type template. Write discipline content neutrally — as that discipline’s content in plain technical general American English, not oriented around how the topic connects to relationality. Those connections emerge from the semiotic network (links, typed relations, cross-domain requires:), not from prose. Include [@citekey] citations for factual claims. Check bibliography.bib for existing entries.

  8. If the note is a discipline page or school page, prioritize the “Methods” section — this is the section most likely to be underdeveloped.

  9. After writing, run /check-note-style on the new file.

  10. Report the full path created and a summary of what was written.