Ask a coding agent for a pop-up dialog and there’s a fair chance it builds one the 2016 way: a stack of divs, a z-index of 9999 and a quiet hope that nobody presses Tab. Chrome thinks that’s a problem worth fixing, and this week it shipped Modern Web Guidance 1.0 to do it. We think it’s the right idea, because we’ve been doing a small version of it on Calendrz for most of this year.
If you build anything with AI, this matters to you. Your agent writes code from what it saw most often in training, and what it saw most often is rarely what’s current.
What Modern Web Guidance 1.0 is
Chrome announced the stable release on 10 November, six months after previewing it at Google I/O. It’s a set of skills that plug web platform expertise, best practices and browser compatibility data straight into coding agents. You install it with one npx command, or through the plugin marketplaces of Claude Code, Codex, Cursor, Copilot, Antigravity, WebStorm and others.
The 1.0 release adds a few things:
- A modernisation workflow that scans existing HTML, CSS, JavaScript and
package.jsonfiles for safe upgrades, and walks the agent through them. - A bigger guide database aimed at what Chrome calls “hundreds of verified AI knowledge gaps”, each with a vetted, cross-browser fix that often swaps custom JavaScript for native HTML and CSS.
- Human review of every guide by subject experts, with a separate accessibility review using real assistive technologies for anything a user sees.
- Public evals comparing agents with and without the guidance.
Firefox and Edge have joined Chrome in backing it, which is the part we like most: advice about the web shouldn’t come from just one browser. Early users report big numbers too. Japanese publishing platform note inc. says pass rates on its modern web checks went from 61% to 94% over 180 runs.
Why coding agents need Modern Web Guidance
The phrase that matters is “knowledge gaps”. A model is a snapshot of the internet, and the internet has far more old tutorials than new ones. So the agent reaches for the pattern it has seen ten thousand times, not the one the platform shipped last year. It isn’t wrong, exactly. It’s just confidently out of date, like a satnav that still sends you down a road that became a cycle lane in 2022.
You don’t fix that by asking more nicely. You fix it by handing the agent the expertise it’s missing, in writing, every time it starts work.
What we do on Calendrz
Calendrz is built with AI agents, and in February our founder, Liviu Tudor, set up the agents, rules and skills they work from. We hit exactly the problem Modern Web Guidance describes, just on a smaller scale.
Our web app runs on a recent version of Angular, a framework that has changed a lot in the last few years. Left alone, an agent happily writes Angular the way most of the internet still does. So our frontend agent comes with roughly a thousand lines of guidance: use signals, standalone components and the built-in @if and @for blocks; write strict TypeScript with no any; never put a click handler on something that isn’t a button or a link. The backend agent gets the same treatment for Java and Spring.
The most useful section isn’t the long list of good practice. It’s the short list headed “Anti-Patterns to Avoid”: no NgModule for new code, no *ngIf or *ngFor, no Protractor for end-to-end tests because it’s deprecated. Each line is a knowledge gap, written down once so no session has to stumble into it again. That’s the same idea as Chrome’s guide database, minus the panel of experts. Our panel is one founder and a growing sense of déjà vu.
It isn’t only code. Our brand skill teaches agents our vocabulary, so a screen they build says “availability mirroring” and “connected accounts”, never “calendar sync”. To the agent, that’s just another knowledge gap: the whole internet calls it syncing, and we don’t, because Calendrz doesn’t copy your events around. It mirrors your busy time as private blocks.
Two lessons came out of it:
- Write down the “don’ts”, not just the “dos”. Agents already know plenty of good practice. What they lack is knowing which of it has gone stale.
- Keep the guidance with the code. Our rules live in the same repository and get reviewed and changed like any other file. When the framework moves on, the guidance moves with it.
What to take from it
We think this is where software engineering is heading: people describe what they want and how it should be built, and agents write, test and ship the code. In that world, the guidance files are the real engineering work. Modern Web Guidance is Chrome, Firefox and Edge writing a shared chapter of them for everyone who builds for the web.
If you build with agents, install it. Then write your own chapter for the parts only you know: your framework versions, your naming, your words. Your agent will thank you, or at least stop reaching for z-index 9999.
And if keeping several calendars from double-booking you is your own knowledge gap, try Calendrz free. Connect your accounts once, and auto-blocking keeps every calendar showing when you’re busy, without sharing what you’re busy with 🙂







