Get the HTML Spec Operator Playbook

Nine sections, every artifact you need to adopt Thariq Shihipar's HTML-as-spec workflow — the same approach Anthropic's Claude Code engineering lead walked through with his 20-example companion site. Why markdown breaks at scale (no tabs, no collapse, dead-on-share, read-only). The five reasons HTML wins for deliverables (information density, readability at scale, sharing efficiency, two-way interaction, joy factor — with the honest 2-4× token tradeoff). The 9 categories of HTML spec work — Planning, Code Review, Design System, Prototyping, Diagrams, Decks, Research, Reports, Custom Editors — each with a paste-ready example prompt. The single-file constraints prompt block (inline CSS, inline JS, base64 images, system fonts, no network, WCAG 2.2 AA) you drop into every HTML generation prompt. The "interview me" trigger that turns Claude into a discovery partner instead of a one-shot generator, with the operator rule to print back the inferred spec before generating. The Markdown ↔ HTML companion workflow with a paste-ready /regen slash command and the sync rule that prevents drift. The template + JSON-data pattern — three sections (data block, template tags, render script) that turn one-off artifacts into reusable mini-applications with clean Git diffs. Five paste-ready prompts (Onboarding Variants, PR Review, Technical Explainer, Deploy Flowchart, Incident Report) — copy, customize, ship tonight. Five carve-outs where markdown still wins (READMEs, Slack snippets, RAG-indexed docs, git blame, short memos) with the operational rule. And the 5 mistakes from the first 30 days — token cost spiral, refeed prompt cost, accessibility skip, HTML for collab docs, forgetting print CSS — each with the exact fix.

By submitting, you'll be subscribed to the Hyperautomation AI Report newsletter — one practical AI email per week. Unsubscribe anytime.

Free. No spam. Unsubscribe anytime.