NoizuPromptLingo: Command for Claude Code

Annotation Instructions.

THE ANNOTATION LOOP

For each annotation, perform these two operations in sequence before moving to the next annotation:

┌─────────────────────────────────────────────────────────────┐
│                                                             │
│   FOR EACH ANNOTATION:                                      │
│                                                             │
│      1. Insert [^marker] in annotated file                  │
│      2. Append [^marker]: definition to footnotes file      │
│                                                             │
│   THEN move to next annotation and repeat.                  │
│                                                             │
│   ─────────────────────────────────────────────────────     │
│                                                             │
│   DO NOT: Insert all markers, then append all definitions    │
│   RIGHT: Insert marker → append definition → next marker    │
│                                                             │
└─────────────────────────────────────────────────────────────┘

CORRECT WORKFLOW

flowchart TD
    A[Copy original to annotated file] --> B[Identify first annotation location]
    B --> C[Insert Single marker in annotated file]
    C --> D[Append Single definition to footnotes file]
    D --> E{More annotations?}
    E -->|Yes| F[Identify next annotation location]
    F --> B
    E -->|No| G[Done]

FOOTNOTE DEFINITION FORMAT

Single-Line Footnote

[^marker-id]: Short definition on the same line.

---

Multi-Line Footnote (4-SPACE INDENT)

For multi-line definitions, put the marker on its own line, then indent all content with 4 spaces:

[^marker-id]:
    First line of the definition starts here with 4-space indent.
    
    Additional paragraphs also indented 4 spaces.
    
    **Markdown formatting** works normally within the indented block.
    
    - Lists work too
    - Just keep the 4-space indent

---