Inline, git-friendly feedback on markdown documents with Claude
Overview · Install · Syntax · Editor setup
Color makes the two voices easy to tell apart: your comments in gold (#968748), Claude’s in teal (#3C8C8C).
The simplest option is to ask Claude Code to “set up VSCode highlighting for iteration markers” or “set up Obsidian highlighting for the vault in notes/”. The skill includes the configs and the steps. You can also do it by hand:
document-iteration-skill/assets/editor-configs/vscode/.vscode/ into your project. If you already have a settings.json, merge the settings into it.jgclark.vscode-todo-highlight).keybindings.json to your user keybindings.Snippets: %% + Tab inserts a comment, %%? a question, %%a APPROVED, and ==( wraps the selection in a token.
document-iteration-skill/assets/editor-configs/obsidian/.obsidian/ into your vault, keeping any existing files.iteration-markers CSS snippet (Settings → Appearance) and the Regex Mark plugin (Settings → Community plugins).Obsidian already treats %% … %% as comments, so the markers stay hidden in reading view.
Settings → Editor → TODO → add these patterns:
\%\%[^%]*\%\%•\%\%>.*<\%\%•==[^=]*\([^)]*\)==syntax match IterationUser /%%[^%]*%%/
syntax match IterationClaude /•%%>.\{-}<%%•/
syntax match IterationHighlight /==[^=]*([^)]*)==/
highlight IterationUser guifg=#968748
highlight IterationClaude guifg=#3C8C8C
highlight IterationHighlight gui=underline