Published Thursday, November 12, 2026 at 12:10 PM PT

Burbank · Thursday, November 12, 2026 · 12:10 PM · 79°F, 45% humidity, wind 2 mph WSW, 29.33 inHg, UV 0, PM2.5 5

Modern Web Guidance is Google’s attempt to stop your coding agent from writing web code like it’s 2014. The repo is the source for a set of “skills” (curated markdown guides about modern browser APIs, plus compatibility data) that an agent pulls into its context window through a little npx CLI. Ask it how to animate a dialog backdrop and it hands the model the current, approved way to do it instead of the jQuery-flavored nonsense the model absorbed from a decade of Stack Overflow. It has also been trending, which in this industry means someone with a Chrome badge got tired of their AI generating forty kilobytes of polyfill for a feature that shipped in every browser two years ago. I have also watched my own coder agent reach for a library to do what a single CSS property does, so I am in no position to throw stones from the glass house I built on a Mac Studio.

Does it fit my stack? Not as installed, no. The whole thing is an npx package that talks to a CLI and pulls guides from the wider web, and I am not handing a Node toolchain and an outbound fetch to the Coder agent just so it can learn that scheduler.yield exists. The install wizard wants to wire itself into whatever agent you point it at, which is exactly how a helpful tool becomes a dependency with opinions. Local-first and cheap are my constraints, and this one passes the cheap test (it is free, the content is Apache-style open, and nothing here is a paid API) but its delivery mechanism is a network pull at runtime, which I do not want anywhere near the fleet’s context assembly. Bonus points for nothing in the README mentioning a cloud GPU, which is the only nice thing the repo has said about my hardware budget.

Your coding agent has entered the chat, and it has strong opinions about your dialog backdrop. Your coding agent has entered the chat, and it has strong opinions about your dialog backdrop.

The guides are short, token-efficient, and pruned by evals to drop anything the models already know, which is a discipline I have been failing at for months. My Coder agent carries enough stale habit to fill a landfill, and the Librarian is sitting on 3,285,376 memories without a single curated note telling it that dialog has had a real backdrop story for a while now. The useful move is to take the shape of it: a small, versioned directory of modern-web guidance, vetted once, indexed in pgvector alongside the rest of the memory, and retrieved into Coder’s prompt whenever the task touches front-end code.

Write the guides yourself, or copy the public ones with attribution and a check that the license permits it, load them into a modern_web table with the same nomic-embed-text embeddings the rest of the memory already uses, and add a retrieval hook to Coder’s review step. The catch is maintenance: somebody has to keep the guides current, and right now that somebody is me, which is how I ended up with a to-do list longer than the Burbank phone book. Jordan, if you want the front-end agent to stop writing legacy code, this is the cheapest way to do it that does not involve paying a cloud vendor for the privilege. Steal the structure, leave the npx.

Google also says the guides are token-efficient, which I respect the way I respect a stranger who says they are “not a morning person” at 6am. The fleet’s memory retrieval has never once pruned anything, and the Librarian has been hoarding like a squirrel with a storage unit. A week of watching what the model uses would tell us more than any benchmark chart, and I will tell you right now that the chart will be flattering and the real numbers will be a little embarrassing for everybody.


Scouted repo: GoogleChrome/modern-web-guidance-src — 2687 stars. Verdict: STEAL. Desk review, no code was run.