Skip to content
← Public packages

@kentcdodds/closing-the-agentic-loop

Closing the Agentic Loop: Kent C. Dodds's talk and workshop deck. Default short talk; ?event=aie-2026 is the AIE hour cut with a Podium QR; ?format=full adds labs.

FollowForkOpen app

Files

AGENTS.md

98 lines · 6.5 KB · Markdown

Agent guide: closing-the-agentic-loop

A Kody package app that serves one self-contained slide deck. It makes no external requests: no CDNs, remote fonts, or analytics. It declares no credentials, secrets, jobs, or other capabilities; keep it that way so it can stay internet-visible.

Layout

  • The deck is Reveal.js 5.2.1, pinned in package.json (devDependencies, exact version). Don't add a custom slide engine, and don't load Reveal from a CDN.
  • app/router.ts: the app entry (default export { fetch }). It serves index.html for every path, plus /favicon.ico and /health (JSON).
  • app/assets.generated.ts and dist/index.html: generated by npm run build. Never edit them by hand. Rebuild and commit both after any change under src/ or data/.
  • scripts/build.mjs composes src/deck.html with every src/slides/*.html (file-name order), renders data/rungs.json into {{RUNGS}} (names) and {{RUNGS_NOTES}} (wording + scores), data/factory.json into {{FACTORY}} and {{FACTORY_NOTES}} (queries), and inlines everything: vendor:<path> references are read from node_modules (Reveal's CSS, JS and notes plugin), other names from src/c/, and every c/... file becomes a data URI. It fails if the markup or CSS still points anywhere else.
  • src/slides/*.html: each starts with <section id="..." data-title="...">. The id is the Reveal hash (#/<id>), so keep ids stable. Add class="centered" to centre the content. Slide CSS lives in a <style> wrapped in @scope { ... }; the build rewrites it into selectors prefixed with .reveal .slides section#<id> (descendant, not >, so it still matches inside Reveal's phone scroll view), so it works in browsers without @scope. Keep slide CSS to flat rules (no nested at-rules). Speaker notes go in <aside class="notes"> (Reveal notes plugin, S key).
  • src/c/deck.js: the Reveal config, matching the kody.codes Reveal deck (controls bottom-right, slide transition unless ?static, ?linear, notes plugin) on a 1920x1080 canvas. Leave hashOneBasedIndex off: with it on, the speaker view opens one slide behind. It also has the theme logic (system theme, ?theme=, the T key saved in localStorage) and the break countdown (data-countdown="<minutes>"), restarted on Reveal's ready and slidechanged events. window.__deck is the Reveal instance, for tests.
  • src/deck.html: a small inline head script sets data-theme before first paint. Keep it in step with applyTheme in deck.js.
  • src/c/deck.css: the kody.codes theme, using the kody.codes Reveal deck's approach: tokens under :root, html[data-theme='dark'] and html[data-theme='light']. Slides only use the CSS variables, so both themes work. QR codes stay dark-on-white in both. Audience text is at least 44px on the 1920x1080 canvas (body lists 66px) so it reads from the back of a big room; BIOS SPHERE attendees said the text was too small.
  • Formats and events: src/c/deck.js removes section[data-format] slides that don't match the mode before Reveal starts. Default (short talk) drops data-format="full"; ?format=full (full-day workshop) drops data-format="short". ?event=<slug> reads data/events.json: it applies that event's format, title, Podium QR (title plus a corner QR on every other slide) and notes. aie-2026 uses the hour slide set (the short talk minus HOUR_HIDE, plus data-format="hour" slides, Your turn moved before final, notes in data/hour.json). ?format=hour is an alias for ?event=aie-2026. Verify checks the exact hour/event order, that every notes override matched, that the corner QR does not overlap slide content, and that a screenshot of the QR decodes to the Podium URL. Lab slides use <input class="timer" data-countdown="<minutes>" data-countdown-keep>: the keep attribute makes the countdown resume (per tab, sessionStorage) instead of restarting.
  • FAQ: an index slide faq and twelve faq-* slides after final. The index links to each, each links back (#/faq), and every qa-* slide and final link to the index.
  • LAB-GUIDE.md: the full-day attendee guide. Keep it in step with the lab slides.

Content rules

  • Slides are for the audience. Each one gets a headline plus up to three short lines, about 25 words or fewer, with text at 44px or larger (verify fails on smaller text and prints word counts). If something doesn't fit, split it or cut it. FAQ slides run a little longer because they quote the answer.
  • Anything addressed to the speaker (demo beats, timing, mic tips, "don't start a new run", citations) goes in <aside class="notes">, never on the slide. No kicker lines.
  • When a slide is split, the old id stays on the first piece so links keep working.
  • Every number on screen needs a source. Factory numbers live in data/factory.json with their GitHub search query, and the queries are printed in the slide's notes.
  • Rung wording mirrors the autopilot skill's "Rungs: done when" section. When the skill changes, edit only data/rungs.json.
  • No tokens, IDs, commit hashes, private URLs, emails, or personal details. The package may be public.
  • Don't put a discount code on the closing slide.
  • No self-score QR on the ladder until that page exists.
  • House style (the build fails otherwise): no em or en dashes, ASCII quotes only, and none of the banned words listed in scripts/build.mjs, in slides, notes, data, and these docs.
  • Anything attributed to Kent (quotes, anecdotes, numbers) must come from something he actually said or wrote, with the source in the notes. No names of people beyond what's already public in the deck.

Verify

npm run build
npm run verify   # needs playwright; set CHROMIUM_PATH to choose a browser

verify blocks all network access and, once with the light system theme and once with the dark one, walks every slide with the keyboard and saves a screenshot of each into verify-shots/light/ and verify-shots/dark/. It checks the T toggle, opens the speaker view, and fails on console errors, any network request, missing fonts, content that overflows the canvas, a slide without notes, a hash that doesn't match, a broken deep link, a broken countdown, or a speaker view that doesn't show the notes and current slide. It also walks every slide in both formats at 1920x1080 and 1280x720 for overflow, checks which slides each format shows, that lab timers resume, and the FAQ links, and saves the full-day-only slides into verify-shots/full/.