@readmodelmag
MODEL

Tools

Modern Web Guidance 1.0, tested: Google's legacy-code scanner caught 1 of 4 old patterns

SummaryWe ran the free legacy-scan from Chrome's Modern Web Guidance on our own Next.js site and on a small file of old-school front-end code we wrote on purpose. It is fast, offline and costs no tokens. It also misses most of what a human reviewer would flag, which Google says up front.

· MODEL Editors · 2 min read

Some links may be affiliate links. Disclosure

MODEL card on a cream background. Red kicker: WE TESTED IT / MODERN WEB GUIDANCE 1.0. Large red text: 1 of 4. Black headline: Legacy patterns flagged in our planted test. Bottom left: MODEL. Bottom right: MODEL test, Nov 15, 2026.
Our own test output, November 15, 2026. Illustration by MODEL. Original. Image source.

What it is. Modern Web Guidance is a free, open-source (Apache-2.0) skill pack from Google's Chrome team that steers coding agents toward modern HTML and CSS instead of custom JavaScript. Version 1.0 shipped Nov. 10, 2026 with 203 use-case guides covering 250 web platform features, and the project is now stewarded by the Chrome, Edge, Firefox and MDN teams (GitHub release (opens in a new tab)). It installs into Claude Code, Codex, Cursor, Copilot and other agents. The new piece in 1.0 is legacy-scan, a local scanner that looks for old patterns in your code with no AI model involved.

What we ran. On Nov. 15 we ran npx modern-web-guidance@1.0.0 legacy-scan twice, with no API key and no agent:

  • Our own site (the Next.js and TypeScript code behind readmodelmag.com, about 97 source files): 0 findings, in under 1 second. The tool checked 33 guides and skipped 6 doc and test files.
  • A planted test we wrote with four old-school patterns: a textarea that resizes itself with scrollHeight, a tooltip toggled with style.display, a scroll listener that calls getBoundingClientRect to reveal a box, and a full-screen "modal" made from a fixed div with a big z-index. It flagged 1 of the 4: the textarea hack, with the exact line (app.js:2) and the fix, CSS field-sizing: content. Run time: 0.6 seconds.

What it fixed (the useful part). For the one hit, npx modern-web-guidance retrieve form-fields-automatically-fit-contents printed a full guide: the CSS fix, plus the gotchas, like setting a minimum and maximum width so an empty input does not collapse. That is the part your agent is meant to read before it edits.

The catch.

  • The scanner itself says it covers only 33 guides, about 20% of the library. The scanner did not flag our tooltip or modal patterns, even though search turns up tooltip, popover and dialog guides for them. It also missed the scroll-reveal listener. Your agent still has to search for the right guide while it works.
  • It reports, it does not edit. There is no fix flag by design (docs (opens in a new tab)).
  • A clean scan is not a clean bill of health. Our 0 means none of the 33 checked patterns showed up, not that our front end is modern everywhere.

The MODEL verdict. Worth one command on any front end an agent has touched: it is free, offline and takes about a second. Treat it as a first pass. The real value is installing the guides so your agent pulls them in while it writes code; the scanner alone catches a narrow slice.

Tested by MODEL Editors on Nov. 15, 2026 with modern-web-guidance 1.0.0. Not sponsored. No affiliate links.

Get three tested tools every Friday

Free, weekly. Unsubscribe anytime.

Sources

  1. Modern Web Guidance 1.0: The web platform expertise your coding agent is missing

    Chrome for Developers (Google)

  2. Release v1.0.0

    GoogleChrome on GitHub

  3. How Modern Web Guidance modernizes your codebase

    Chrome for Developers (Google)

  4. modern-web-guidance on npm

    npm

FREE · EVERY WEEK

The top AI tools this week, tested.

Every week MODEL's editors pick the AI tools worth your time, try them hands-on, and tell you what's good, what's not, and who it's for. Free, in your inbox.

Free. Unsubscribe anytime. Our picks are editorial and can't be bought.