Press Esc to close

Chrome releases Modern Web Guidance to keep AI web code current

Chrome releases Modern Web Guidance to keep AI web code current
Official Modern Web Guidance 1.0 artwork with the project mark on a blue field

Image: Chrome for Developers, 2026. Official artwork from the Modern Web Guidance 1.0 announcement.

Google Chrome has released version 1.0 of Modern Web Guidance, a skill pack that feeds current web platform advice into AI coding agents. An early preview appeared at Google I/O in May. In a November 2026 post on the Chrome for Developers blog, the Chrome team called this the stable release. The pack is meant to steer agents away from legacy JavaScript workarounds and toward native HTML, CSS, and web APIs, with browser compatibility data built in. The project is published under the Google Chrome organization on GitHub. Chrome says version 1.0 is also a cross-browser effort, with teams from Microsoft Edge, Mozilla Firefox, and MDN helping to steward it alongside the web development community.

The release spread on X after don_tech1 shared the official install command and described the project as a way to bring agents up to date. don_tech1 is the person sharing it. The tool itself is from Google Chrome. Some figures in that post, including a jump from 56 percent to 88 percent and a count of 212 features, do not match the project's latest published snapshot one for one. The details below follow the GitHub repository and Chrome's own documentation.

Modern Web Guidance is for people who already use a coding agent to write or modernize front-end code, including work in HTML, CSS, client-side JavaScript, accessibility, performance, forms, and related browser APIs. Chrome says it can be installed and used with any coding agent that supports skills. The 1.0 announcement lists plugin marketplaces that include Claude Code, Codex, Cursor, Antigravity, Copilot, WebStorm, Kimi Code, and Grok Build. The repository and the official get-started guide also document installs for the Gemini CLI, the GitHub CLI, the Vercel Skills CLI, and Goose. Chrome also notes that developers have used the guides as a learning resource on their own, not only as fuel for an agent.

The reason the tool exists is spelled out in the repository. Coding agents often default to older patterns because their training data contains a large amount of legacy code. That can lead them to generate bulky JavaScript for tasks that now have native, high-performance platform solutions. Even when a model knows an API exists, the README says, it often lacks the density of modern production patterns. The skill tells the agent to query a local CLI, which then returns a short, expert-curated guide for the task at hand. Search runs offline with a local embedding model and a BM25 engine, and the README says it needs no network calls and no API keys. The npm package is self-contained. The project uses npx so the advice does not go stale, while the CLI itself can work offline.

The current README lists 250 modern web features, grouped as 140 in CSS and layout, 36 in HTML and DOM, and 74 in JavaScript and APIs. Coverage includes view transitions, container queries, popovers and dialogs, passkeys, Interaction to Next Paint diagnostics, and on-device language APIs, among other topics. A second optional skill pack covers Chrome extensions, including Manifest V3, background workers, and Chrome Web Store publishing. Guides are written to be short, and the project says it prunes advice that models already follow. Recommendations can be tailored to a project's Baseline target. If no target is set, Chrome's docs say the tool defaults to Baseline Widely available.

Official Modern Web Guidance eval dashboard graphic comparing results with and without the skill

Image: Google Chrome. Official social image for the Modern Web Guidance evaluation dashboard, comparing guided and unguided pass rates.

Chrome and the repository publish evaluations that compare agents with the skill turned on and off. The README's latest snapshot, dated November 8, reports that Claude Code with Opus 5.5 moved from a 57 percent unguided pass rate to 88 percent with guidance, a gain of 31 percentage points, across 215 tasks. Codex CLI moved from 54 percent to 82 percent, a gain of 28 points. Antigravity CLI with Gemini 4 Argon moved from 58 percent to 94 percent, a gain of 36 points. Chrome's get-started guide also says that, on average, early results show a 37 percentage point improvement in adherence to modern best practices, and that results can vary by project, model, prompts, and tooling. A public evaluation dashboard has the full per-agent and per-guide breakdowns. Chrome's 1.0 post also published case studies. In one of them, note inc. reported that a 180-run evaluation on its production codebase raised pass rates on modern web checks from 61 percent to 94 percent.

Once the skill is installed, the usual loop is simple. The agent activates Modern Web Guidance for a relevant web task, searches with a short description of the capability, then retrieves the matching guide by ID and uses that guidance while writing code. For an existing project, version 1.0 adds a modernization workflow. A local scan of HTML, CSS, JavaScript or TypeScript, and package.json looks for high-confidence legacy patterns, then the agent can retrieve the matching guides and apply upgrades. Chrome says this first release checks a limited, carefully tested subset of the catalog, about 20 percent of the guides, so that the matches stay predictable. The official blog shows a prompt of the form below for asking an agent to modernize a directory.

/modern-web-guidance Modernize the code in this directory
Official Get started with Modern Web Guidance cover art showing a laptop and connected nodes

Image: Chrome for Developers, 2026. Official cover from the Get started with Modern Web Guidance documentation.

How to set it up

The published npm package lists a Node.js requirement of version 22 or later. From a project directory, the recommended install, confirmed in both the repository and the Chrome blog, is the official CLI. Chrome says installing this way enables automatic updates. The command runs an interactive wizard.

npx modern-web-guidance@latest install

If the project includes Chrome extension work, the repository and the official get-started guide recommend the same command with a flag that opens a pack picker. The two packs are modern-web-guidance, described as about 205 tokens, and chrome-extensions, described as about 175 tokens.

npx modern-web-guidance@latest install --choose

If an earlier version is already installed, Chrome's 1.0 announcement and the README both give this update command.

npx modern-web-guidance@latest update

The CLI can also be tried without installing the skill, which is useful for reading a guide or scanning a repo first.

# Search for relevant guides
npx modern-web-guidance@latest search "animate a dialog modal backdrop"

# Retrieve a guide by ID
npx modern-web-guidance@latest retrieve "animate-to-from-top-layer"

# Scan a codebase for legacy patterns to modernize
npx modern-web-guidance@latest legacy-scan .

Chrome's get-started guide also lists agent-specific installs. The docs warn that most of those routes do not support automatic updates the way the official CLI does. Commands below are copied from the repository, the official docs, or both.

For Claude Code, the official get-started guide gives these shell commands. The repository also lists the same steps as slash commands inside the product, plus a /plugin step to enable AutoUpdate and a /reload-plugins command.

claude plugin marketplace add GoogleChrome/modern-web-guidance
claude plugin install modern-web-guidance@googlechrome

For OpenAI Codex, the repository and the official docs agree on the following.

codex plugin marketplace add GoogleChrome/modern-web-guidance
codex plugin add modern-web-guidance@googlechrome

For GitHub Copilot CLI, both sources list these slash commands, first to add the marketplace and then to install the plugin.

/plugin marketplace add GoogleChrome/modern-web-guidance
/plugin install modern-web-guidance@googlechrome

For Google Antigravity's CLI, the repository and the official docs give this command. The docs also say Antigravity users can enable modern-web-guidance during setup, or later under Settings, Customizations, then Build with Google Plugins.

agy plugin install https://github.com/GoogleChrome/modern-web-guidance

For Grok Build, the repository lists this command, which is also in the official docs under the name Grok.

grok plugin install https://github.com/GoogleChrome/modern-web-guidance --trust

For Kimi Code, both sources list this slash command.

/plugins install https://github.com/GoogleChrome/modern-web-guidance

The official get-started guide, though not the README, also documents a Gemini CLI install.

gemini extensions install https://github.com/GoogleChrome/modern-web-guidance --auto-update

Other documented options include the GitHub CLI, the Vercel Skills CLI, and Goose.

gh skill install GoogleChrome/modern-web-guidance

npx skills add GoogleChrome/modern-web-guidance

goose plugin install https://github.com/GoogleChrome/modern-web-guidance --auto-update

Cursor and JetBrains WebStorm are named in Chrome's 1.0 announcement as supported marketplaces. The official docs say WebStorm users can install the skill from Skill Manager under Settings, AI Assistant, Skills. The recommended CLI install above remains the path documented for agents that support skills in general, including when a product-specific command is not listed in the repository.

A few settings help get more out of the tool after install. To adopt experimental Origin Trial APIs, the repo and the official docs give this command, which writes an allowOriginTrials flag to an optional .mwgrc file in the project root, or to a user-level fallback at ~/.mwgrc.

npx modern-web-guidance@latest set-allow-origin-trials

A similar command unlocks guides for volatile single-engine features. Chrome cautions that those features may still change.

npx modern-web-guidance@latest set-allow-volatile-features

For Baseline, the official docs suggest adding a line to AGENTS.md or CLAUDE.md that states the project's target, for example Baseline 2024. If that is left unset, the default is Baseline Widely available.

On privacy, the README says Google collects anonymous usage information, including installation counts, the calling agent name, guide retrieval IDs, and CLI search queries generated by the agent. It says raw user prompts are not collected. To opt out, set this environment variable in a shell profile.

export DISABLE_TELEMETRY=1

Chrome recommends pairing Modern Web Guidance with Chrome DevTools for agents. The first tool is meant to supply up-front expertise. The second is meant to give the agent runtime visibility so it can verify, debug, and optimize the result, including performance traces, animation checks, reduced-motion behavior, and memory use. The skill is not a substitute for reviewing the diff. After the agent applies a guide or a modernization scan, it is still worth reading the changed files, especially around accessibility, security, and fallbacks. The repository licenses software under Apache License 2.0, and documentation under guides/ under Creative Commons Attribution 4.0. This GitHub repo is a publish target. Issues and contributions, the project says, should go to the source repository.

At the time of this writing, Modern Web Guidance 1.0 is the stable, documented way Chrome is asking developers to keep coding agents current on the web platform. The one-line install is real, and the published evaluations show sizable gains on the project's own tests. Those tests are not a guarantee for every codebase. The surest way to make full use of the tool is to install it with the official CLI, let the agent search and retrieve guides for actual front-end work, run a legacy scan on older code when that is the goal, and then verify what the agent changed.

Comments

Reader support

No ads. Just independent reporting.

Techcity Authority runs without advertising. Hosting, tools, and the hours behind each piece are supported by readers instead. Even a small contribution goes a long way — and every supporter is credited by name below for the month they give.

Support the site

Monthly via PayPal · cancel anytime

Secure checkout on PayPal. Your name appears here for the month you support.

This month’s supporters

    No supporters yet this month — yours could be the first name here.