| name | comment-mode |
| description | Granular feedback on drafts without rewriting. Generates highlighted HTML with click-to-reveal inline comments. Use when user says "comment on this", "leave comments on", "give feedback on", or asks for feedback on a draft. Supports multiple lenses—editor feedback, POV simulation ("as brian would react"), or focused angles ("word choice only", "weak arguments"). A granular alternative to rewrites that lets users review feedback incrementally without losing their voice. |
Comment Mode
Generate highlighted HTML with click-to-reveal comments for granular feedback on text. Alternative to rewrites—user keeps their voice, reviews feedback incrementally.
When to Use
- User says: "comment on this", "leave comments on", "give feedback on"
- User pastes text and asks for feedback/critique
- User wants targeted feedback without a full rewrite
Clarify Before Commenting
Use AskUserQuestion to clarify scope when the request is ambiguous. Avoid over-commenting (overwhelming) or under-commenting (missing the point).
Clarify when:
- No lens specified → ask what angle they want
- Long document → ask if they want full coverage or just key sections
- Unclear audience → ask who the recipient is (affects POV comments)
Skip clarification when:
- Lens is explicit ("comment on word choice only")
- Document is short (<500 words)
- Context is obvious from conversation
Example clarification:
User: "comment on this"
[long doc, no lens specified]
→ Use AskUserQuestion:
"What should I focus on?"
Options:
- "Editor feedback (structure, clarity, word choice)"
- "Recipient POV (how [person] would react)"
- "Specific angle (tell me what)"
Lenses
| Lens | Color | Comment style |
|---|
| Editor | Yellow (#fff3cd) | observations, suggestions: "weak opener", "add proof here" |
| POV (as person) | Blue (#e3f2fd) | reactions from that person's perspective: "i know this already", "legal would freak out" |
| Focused | Yellow | specific angle only: "word choice", "tone", "weak arguments" |
Comment Style
- Always lowercase
- Short (5-15 words)
- Smart about type: observations when noting, suggestions when alternatives help, reactions when simulating POV
- Only comment where there's something worth saying—sparse beats exhaustive
Output Rules
DO:
- Write to
_private/views/{name}-comments-temp.html
- Open with
open _private/views/{name}-comments-temp.html
- Use highlight colors matching the lens
- Keep comments sparse and high-signal
DO NOT:
- Comment on everything—only where there's an obvious edit or insight
- Over-explain in comments—keep them punchy
- Mix lenses in one output—pick one and stick to it
Template
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>{title}</title>
<style>
* { box-sizing: border-box; }
body {
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
max-width: 700px;
margin: 0 auto;
padding: 40px 20px;
line-height: 1.7;
color: #1a1a1a;
background: #fafafa;
}
h1, h2, h3 { margin-top: 2em; font-weight: 600; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; color: ; }
{ : ; }
{
: {highlight-bg};
: ;
: ;
: pointer;
: solid {highlight-};
: background ;
}
, {
: {highlight-hover};
}
{
: none;
: {comment-bg};
: ;
: ;
: ;
: ;
: ;
: ;
}
{ : block; }
{
: none;
: solid ;
: ;
}
{
: fixed;
: ;
: ;
: ;
: ;
: ;
: (,,,);
: ;
: ;
}
{content with highlighted phrase}
{count} comments · click highlights to reveal
Color Reference
Editor lens (yellow):
.highlight { background: #fff3cd; border-bottom: 2px solid #ffc107; }
.highlight:hover, .highlight.active { background: #ffe69c; }
.comment { background: #1a1a1a; }
POV lens (blue):
.highlight { background: #e3f2fd; border-bottom: 2px solid #2196f3; }
.highlight:hover, .highlight.active { background: #bbdefb; }
.comment { background: #0052cc; }
Workflow
- User pastes text + asks for comments
- If ambiguous: Use AskUserQuestion to clarify lens/scope
- Read text, identify key phrases worth commenting on (sparse, high-signal)
- Generate HTML with highlights and
data-comment attributes
- Write to
_private/views/{name}-comments-temp.html
- Run
open _private/views/{name}-comments-temp.html
Examples
Editor lens:
User: "comment on this, focus on word choice"
→ Yellow highlights, suggestions like "vague, try 'specifically'" or "jargon, simplify"
POV lens:
User: "comment on this as brian would react"
→ Blue highlights, reactions like "i already know this" or "legal would push back here"
Focused lens:
User: "leave comments on this, only flag weak arguments"
→ Yellow highlights on weak claims, comments like "needs evidence" or "assumes too much"
Sparse/sharp lens:
User: "comment only where there's an obvious fix"
→ Minimal highlights, only typos, missing words, or clear improvements
