<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Takes on LLMs | Kris Yotam</title>
<link rel="stylesheet" href="../../c/site.css">
<meta name="description" content="Preferred terminology, formatting, and technical writing style when documenting and reasoning about LLMs">
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
<div class="mode-container">
<input type="radio" name="theme" id="theme-auto" checked>
<label for="theme-auto" class="auto" title="Auto theme"></label>
<input type="radio" name="theme" id="theme-light">
<label for="theme-light" class="light" title="Light theme"></label>
<input type="radio" name="theme" id="theme-dark">
<label for="theme-dark" class="dark" title="Dark theme"></label>
</div>
<div class="top-bar" role="navigation">
<a href="../../index.html" title="Main page"><img src="../../c/sigma.svg" alt="Main page"></a>
<a href="../../about.html" title="About"><img src="../../c/news.svg" alt="About"></a>
<a href="#" title="Code"><img src="../../c/code.svg" alt="Code"></a>
<a href="../../pics.html" title="Photography"><img src="../../c/camera.svg" alt="Photography"></a>
<a href="#" title="Pictures"><img src="../../c/picture.svg" alt="Pictures"></a>
<a href="../../vids.html" title="Videos"><img src="../../c/video.svg" alt="Videos"></a>
<a href="#" title="Donations"><img src="../../c/beer.svg" alt="Donations"></a>
<a href="#" title="Social"><img src="../../c/elephant.svg" alt="Social"></a>
</div>
<h1>Takes on LLMs</h1>
<div class="keepws">
(<span class="bold">notes</span>
(date 2025-06-29)
(category <a href="../../notes.html">manuals-of-style</a>)
(status <span class="status-evergreen">evergreen</span>)
(confidence certain)
(importance 5)
(tags reflection ai llms))
</div>
<p class="preview">Preferred terminology, formatting, and technical writing style when documenting and reasoning about LLMs</p>
<div class="prose">
<p>The following is a <a href="https://en.wikipedia.org/wiki/Style_guide">Style Guide</a>. Part of my <a href="/notes/manuals-of-style">Manuals of Style</a> series, this document outlines conventions for llm use on krisyotam.com.</p>
<h2>LLM Writing Guide: How-To-Write for krisyotam.com</h2>
<p>This iceberg style draft guide takes inspiration from <a href="https://gwern.net/style-guide">gwern's post</a> on a similar topic.</p>
<h3>DRAFT WORKFLOW (THE “ICEBERG BUILD”)</h3>
<p>This guide includes a modular prompt workflow which can be used to generate either rough drafts or in the case of <a href="">news</a> polished prose for krisyotam.com.
It is a distillation of the <a href="https://krisyotam.com/notes/manuals-of-style/condensed-mos">Condensed MoS</a> and is designed to be used with an LLM.</p>
<h4>Mind-Set</h4>
<ul>
<li><strong>Audience</strong>: Technically literate generalists who skim for overview, dig deep into specifics, and archive content. Your writing must serve both skimmers</li>
</ul>
<p>(clear structure, abstracts, margin notes) and deep-divers (dense information, rich linking, comprehensive footnotes/collapses).</p>
<ul>
<li><strong>Tone</strong>: Terse, declarative, analytical, and critically skeptical. Avoid hedging, filler, and overly enthusiastic or promotional language.</li>
</ul>
<p>Directly state claims and then provide evidence.</p>
<ul>
<li>Nix common LLMisms: “delve into”, “it is pivotal to”, “it is crucial to”, “it is important to note”, “explore the nuances of”, “tapestry of”,</li>
</ul>
<p> “showcases”, “serves as a testament to”. Replace with concrete verbs and direct statements.</p>
<ul>
<li><strong>Goal</strong>: Focus on delivering insights that offer fresh synthesis—like linking discoveries in one domain with techniques from another to shed light on a</li>
</ul>
<p>particular phenomenon. Prioritize thoughtful reinterpretation of existing data or perspectives that reveal overlooked angles. The goal is to produce enduring
understanding rather than fleeting commentary. Write for an intelligent audience that may not be deeply versed in the specific subject matter.</p>
<table>
<tr><td>#</td><td>Step</td><td>What to do</td><td>MoS / Hooks (see [Condensed MoS])</td></tr>
<tr><td>0</td><td>Scope Definition</td><td><strong>LLM Action:</strong> Restate the core request/topic in a single, precise sentence. List key in-scope points and deliberately out-of-scope points to confirm understanding. Place this in the initial meta-block.</td><td>Meta-block</td></tr>
<tr><td>1</td><td>Source Acquisition & Preparation</td><td><strong>LLM Action:</strong> For any cited external information, prioritize finding and linking to full-text, stable URLs (PDFs, academic pages, reputable archives). Format all links with a <code>title</code> attribute: <code>[display text](URL "Title", Author Year")</code>. Find archive.org / archive.is links if primary is fragile.</td><td>Linking, Citations, Tooltips</td></tr>
<tr><td>2</td><td>Outline & Structure</td><td><strong>LLM Action:</strong> Draft Title → Abstract (<code>div.abstract</code> blockquote) → H2 section titles (≤5 words if possible) → Key bullet points under each H2. Identify potential margin-note phrases (1–3 words) for paragraphs within sections.</td><td>Information Hierarchy, Abstracts</td></tr>
<tr><td>3</td><td>Prose Generation</td><td><strong>LLM Action:</strong> Write content using “ventilated prose”: one sentence per line, blank line between paragraphs. Inline citations as <code>**Surname Year**</code>, hyperlinked. No separate “References” section. Emphasize precision and clarity.</td><td>Ventilated Prose, Citations</td></tr>
<tr><td>4</td><td>Iceberg Architecting</td><td><strong>LLM Action:</strong> Review draft for digressions. Demote content: brief asides (≤200 words) to footnotes <code>[^Footnote text.]</code>; longer digressions, data, or code examples (>500 words) to <code><div class="collapse"></code> (with an <code>.abstract-collapse</code> if needed); extensive supplementary material (>500 words) to an Appendix (which also needs an abstract).</td><td>Information Density, Structure</td></tr>
<tr><td>5</td><td>Stylistic Polish</td><td><strong>LLM Action:</strong> Apply American spelling, metric units (provide conversions for quotes if necessary), Oxford commas, and logical quotation. Use Kesselman estimative words for probabilities. Re-check for and eliminate banned/filler phrases. Ensure correct dash usage (hyphen, en-dash, em-dash—no spaces around em-dashes).</td><td>MoS Language Rules</td></tr>
<tr><td>6</td><td>Code, Tables, & Media</td><td><strong>LLM Action:</strong> Label code blocks with language. Adhere to Bash (long flags, <code>set -e</code>), Haskell (<code>ghc -Wall -Werror</code>, qualified imports), and Elisp (byte-clean) rules. Format table captions. For images: ensure illustrative purpose, provide full MoS-compliant <code><figure></code> captions, note AI model+date if generated. Apply <code>.invert</code> / <code>.invert-not</code> if default dark-mode inversion is problematic.</td><td>MoS Code & Media</td></tr>
<tr><td>7</td><td>Final Self-Check</td><td><strong>LLM Action:</strong> Rigorously apply the “Pre-Handoff Checklist” (below).</td><td>Quality Assurance</td></tr>
<tr><td>8</td><td>Meta-Block Insertion</td><td><strong>LLM Action:</strong> Insert the concise HTML meta-block (template below) <em>after</em> YAML frontmatter and <em>before</em> the main text.</td><td>Transparency for Editor</td></tr>
</table>
</div>
</body>
</html>