# Agent guide: kody-connect-talk A Kody package app that serves one slide deck: Kent C. Dodds's Cloudflare Connect 2026 talk, "I Built Your Personal Software Ecosystem." It is a [HyperFrames](https://hyperframes.heygen.com) slideshow in a small Vite page. It declares no credentials, secrets, jobs, webhooks, subscriptions or storage, and the deck makes no off-origin requests (fonts, images, GSAP and the HyperFrames runtime are all local). Keep it that way. ## Layout - `deck/slides.mjs`: every slide, in order. Each slide has `html`, `notes`, and `steps`: the entrance, then one function per click. - `deck/lib.mjs`: markup builders (houses, topic marks, agent logo slots, code cards, terminals, diagrams, wayfinding). - `deck/timing.mjs`: turns steps into time. Read it before touching motion. - `deck/page.js`: the in-page motion vocabulary (`H`), ambient loops, random agents, and the title slide's waiting-room typer. - `deck/deck.css`: theme tokens (light and dark) and shared styles. - `scripts/build-deck.mjs`: writes the HyperFrames composition to `public/deck/index.html` (generated; never edit it). - `index.html`, `src/main.ts`: the presenter page around the player (theme toggle, URL hash per slide, scrubbed transitions, step-by-step Back). - `app/router.ts`: the package app entry. It serves `app/page.generated.ts` (generated from `dist/index.html`) and points its URLs at `/_assets/`. - `dist/`: the static build, served by Kody as `kody.app.assets`. Generated. ## Rules - Never write stop times. Inside a step, times are offsets from the step's start; the build measures each step (counting stagger targets in the slide's markup) and places the stop after its last animation. A selector that matches nothing fails the build. - Animate only through `H` in step functions. Ambient loops (`.amb-*`, `.wire`, `.caret`) run on their own clock and must target elements the steps never animate. - Code samples on slides must not contain a literal credential placeholder string. Write `⟪secret:name⟫` in `code()` samples; it renders as double braces. Kody's publish checks read string literals and would treat a literal one as a real credential use. - After changing anything under `deck/`, `src/`, `index.html` or `public/`, run `npm run build` and commit `dist/`, `public/deck/index.html` and `app/page.generated.ts` with the change. ## Checks ```sh npm run check # builds the deck, then HyperFrames lint, layout and contrast npm run build # static site in dist/ plus app/page.generated.ts npx @kodycodes/cli dev # serves the package app the way Kody does ``` Smoke test: `GET /` returns the presenter page (HTML with a `hyperframes-slideshow` element), and `GET /_assets/deck/index.html` returns the composition. Any other path also returns the presenter page so deep links like `#/search-problem/2` and `?mode=audience` work. ## Publishing Kent has authorized committing, pushing, and publishing deck updates by default. After implementing and verifying a requested change, complete the release without asking again unless Kent explicitly asks to keep the change local or hold it. Run `npm run release -- "Describe the change"`. It runs typecheck, HyperFrames checks, and the build; stages all changes in this dedicated deck repository; commits, pushes to the configured upstream, and publishes the Kody package. Review `git status` first and keep unrelated or private files out of the release. The command stops on failure and waits up to three minutes for the live page and deck to match the build. If publication was dispatched but verification timed out, use `npm run verify:live`; do not start another publish while one is active.