# Agent guide: cloudflare-connect-personal-software-ecosystem A Kody package app that serves one self-contained slide deck for Kent C. Dodds's Cloudflare Connect 2026 lightning talk. It makes no external requests: no CDNs, remote fonts, hotlinked images, or analytics. It declares no credentials, secrets, jobs, webhooks, or other capabilities; keep it that way so it can stay internet-visible. It is a fork of the deck in `kentcdodds/kcd-content` at `events/personal-software-ecosystem/slides/`. That repo and its pages.dev deployment are separate; never edit them from here. ## Layout - The deck is [Reveal.js](https://revealjs.com/) 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/`. - `scripts/build.mjs` composes `src/deck.html` with every `src/slides/*.html` (file-name order), wraps them in Reveal vertical stacks from `src/slides/groups.json` (one array of slide ids per column, mirroring the source deck's groups), and inlines everything: `vendor:` references are read from `node_modules` (Reveal's CSS, JS and notes plugin), other names from `src/c/`, and every `c/...` file (including `url(c/...)` in inline styles) becomes a data URI. It fails if `groups.json` misses a slide, lists one twice, or reads in a different order than the files (so Space order and slide numbers match the files), if markup or CSS points anywhere else, if any owned file or the output contains an em dash (U+2014), or if visible slide text or notes contain "used to", "now", "switched", "removed" or "we moved". - `src/slides/*.html`: each starts with `
`. The id is the Reveal hash (`#/`), so keep ids stable. Each file is one slide; the build adds the outer stack `
`, so never nest sections in a slide file. A new slide goes in the column for its topic in `groups.json`. Slide CSS in a `