What if your livestream layout was just a web app? Sergey will show how HTML, CSS, and JavaScript can power interactive live-streaming experiences inside OBS’s embedded Chromium browser and how WebSockets and Cloudflare Workers can turn viewers into active participants.

Coding agents are only as effective as the context they can see—and for long-lived software, the repository is their real prompt. This practical talk explores how clear specifications, enforceable constraints, observable acceptance criteria and fast feedback loops can turn repeated AI mistakes into improvements that compound over time.

Most teams hear "AI design system" and reach for the thing they already know: a component library, now with a chat panel bolted onto it. I think that's the wrong shape. A design system in an AI-assisted codebase isn't a catalogue of components; it's a set of architectural contracts that a coding agent can actually be held to. Tokens, composition rules, and constraints that are legible to a model, not just to a designer in Figma.

The talk walks through what that looks like in practice: what an agent gets wrong when your system is only documented in prose, how to encode intent so the generated code is boringly consistent instead of plausibly wrong, and where the boundary sits between what you let a model generate and what you pin down by hand.

What attendees can expect to take away:

It's aimed at frontend and product engineers, and at design-system maintainers wondering what to do about all this. No prior AI-tooling experience needed.