Contents › Issue 029

Developers would rather write docs for robots than for each other

A post about committing Claude's handoff notes tops Hacker News, a technical writer teaches a 7B model to write like a 1995 Microsoft manual, and Cursor turns agent canvases into a design surface.

Today's art direction

Help Viewer / Three-Pane Manual Docs

A 1998 help viewer on a teal desktop: chrome bevels outside, book typography inside.

Today's page is built like the help viewers that shipped with late-90s software: one application window on a dithered teal desktop, a contents tree on the left, a topic pane on the right. The chrome is cheap to build honestly, the whole bevel system is two box-shadow colors, and the type costs nothing: Istok Web, Gelasio, and Cousine are hosted stand-ins for Verdana, Georgia, and Courier, the faces readers' systems shipped with in 1998. Fitting, since one of today's stories is a language model trained to write like the manuals this window used to hold.

title barcontents treebevel chrometopic pane note boxfigure captionstatus barmetric-compatible type

Contents › Tooling

What shipped

---

Cursor 3.7 adds Design Mode to canvases

cursor.com · June 4

Agents in Cursor build interactive artifacts called canvases: dashboards, reports, internal tools. Design Mode lets you select and annotate UI elements inside a canvas to direct the next edit, the way browser-based agent tools already do, and a new context report renders the agent's token usage as a canvas you can interrogate.

Vercel wires Shopify into v0

vercel.com · June 4

One CLI command creates a free Shopify test store with credentials configured, you build the storefront with v0, and you claim the store when it is ready to launch. Connecting existing stores is listed as coming soon.

Anthropic's vulnerability-hunting harness goes open source

github.com · front page of Hacker News this week

A reference pipeline that scans a codebase for vulnerabilities in a recon, find, verify, report, patch loop, each agent sandboxed in its own container, plus Claude Code skills for threat modeling and triage you can run interactively.

Contents › Technique

Style transfer, vintage 1995

---

Fine-tuning an LLM to write docs like it's 1995

passo.uno · Fabrizio Ferri-Benedetti

Ferri-Benedetti fed 37 million words of scanned Microsoft manuals from Bitsavers into QLoRA fine-tunes of Qwen and Llama, about $50 of rented GPU time in total. The style transferred: asked about REST, a concept that postdates the corpus, the strongest 7B model opened like a chapter of the Windows 2000 Resource Kit. Today's design borrows its idiom from his training data.

Ask HN: What is your AI dev stack? (June 2026)

news.ycombinator.com · June 5

A live census of the tools, agents, and workflows working developers actually run, useful for calibrating your own stack against the field.

Contents › Workflow

Commit the handoff doc

---

Mark Jason Dominus noticed programmers complaining that colleagues happily write detailed agent-instruction files after years of refusing to document for humans. His response, on his blog and on the front page of Hacker News today: stop throwing that writing away.

1. Have the agent maintain a handoff document while you work: what was planned, what was done, what is left.
2. At the end of the project, ask it to write a structured overview of the problem and the changes, from scratch, not just running notes.
3. Review and edit it like work you are signing, then commit it to the repo where future readers, human or otherwise, can find it.

“If you have Claude write down notes, check them into the repo when you’re done. It probably can’t hurt and it might help.”

Mark Jason Dominus, The Universe of Discourse

Contents › Prompt Lab

Recreate this page

---

Paste this into your AI design or build tool to reproduce today's visual system.

Design a single self-contained HTML page styled as a late-1990s software
help viewer, the kind that shipped as a compiled manual with Windows 98
software.

PAGE ARCHETYPE: a help-viewer docs topic page. The entire page lives
inside one beveled application window centered on a dithered teal
desktop. Window chrome, top to bottom: a navy-to-blue gradient title
bar with the site name, a menu bar of plain text links, then a two-pane
body: a left Contents tree and a right topic pane.

COMPONENTS: build the Contents tree from real anchor links with
closed-book and page icons drawn in CSS, plus/minus expander squares,
and a navy selection bar on the hovered row. In the topic pane use
breadcrumbs (Contents > Topic), bold headings over a thin gray rule,
figures with sunken borders and numbered captions, a pale yellow Note
box with a 1px tan border, a Courier-style code block, prev and next
topic links, and a sunken status bar at the window's foot.

PALETTE: dithered teal desktop #0F7268, warm chrome gray #C8C4BA with
#FFFFFF and #7A766A bevel edges, white content panes, navy #1A2E8C
title bar and headings, hyperlink blue #0B3FBF, note yellow #FFF7CC.

TYPE: Istok Web bold for chrome, headings, and labels (hosted Verdana
stand-in); Gelasio for body prose (hosted Georgia stand-in); Cousine
for code (hosted Courier stand-in).

GUARDRAILS: body text at least 19px with 1.7 line height and WCAG AA
contrast on white. Never set body prose on the teal desktop or gray
chrome. Bevels come from two inset box-shadow colors, not drop
shadows. No readable text inside generated images, no pill radii, no
glow, no gradient text. Give links and tree rows honest hover and
focus states, and disable transitions under prefers-reduced-motion.

Contents › Field Note

ReadMe.txt

---

Contents › Sources

Bibliography

---