Bold Highlights — Scannable Prose
Add bold highlights sparingly — a few key words that carry the article's arc. Bolding in most paragraphs defeats the purpose; a reader should notice a handful of highlights, not a shower.
Inputs
target— path to the article inai-thoughts/docs/(optional). If omitted, apply to the article currently being worked on.
Outputs
- The article file with bold highlights applied.
Procedure
- Read the article and identify its overall arc (the story it tells from start to finish).
- Pick a handful of key arc moments — roughly 5-10 highlights for a full-length article. Good candidates: the opening thesis, one concept per major section, and the payoff or tip the author cares most about.
- Bold the single most essential concept at each chosen moment. Leave most paragraphs un-bolded; bold inside list items only when a decisive list highlight is requested (never routinely).
- Verify: scan only the bolded words from top to bottom. Does a sparse mini-story still hold? If not, move highlights to better moments.
- Regenerate READMEs if the article is registered in
articles.yaml.
Constraints
- Max 1 bold highlight per paragraph. Most paragraphs should have none.
- Target roughly 5-10 highlights per article. A handful the reader can count — fewer is always better. A decisive bolded list is the accepted exception (it can push the total to ~15); when one is used, keep everything outside the list spare.
- Space them out. Don't bold in two adjacent paragraphs — the highlights should feel deliberate, not rhythmic.
- Keep bolded phrases short. 1-3 words max. A single word is ideal.
- Don't bold proper nouns, tool names, or obvious context. Bold the concept, not the thing. Example: bold "ground truth" (the idea), not "OpenCode" (already obvious from context).
- Make list-item bolds decisive, on demand only. Bullets are already scannable; bold inside a list only when the user wants that section's items emphasized (e.g. a Benefit list), with at most one bold concept per item — and never routinely.
- Don't bold the title or sign-off.
Verification
- Roughly 5-10 bold highlights across the whole article; never more than one per paragraph.
- Scanning only the bold words tells a coherent, sparse mini-story.
- No bold in two adjacent paragraphs; list bolds appear only where decisive — no routine list-bolding.
- Article reads naturally — the highlights are meant to be scarce.
Error Handling
- User says no: skip bolding; leave the article as-is.
- Article already has bold highlights: verify they follow the constraints; thin them out if they're too frequent, don't add more.
- User asks for a single highlight (e.g. "highlight one thing"): honor that literally — bold just that concept and nothing else.
- User asks to bold a whole list/section (e.g. a Benefit list): treat it as the decisive exception — bold one core concept per item, keep surrounding paragraphs spare.
- Not an article: never apply to READMEs,
articles.yaml, or files outsideai-thoughts/docs/.
