Modern Web Guidance: current platform advice for coding agents
Modern Web Guidance is a coding-agent skill that retrieves current browser and web-platform advice across 250 features, including compatibility-aware fallbacks.
Skill details
npx skills add GoogleChrome/modern-web-guidance --skill modern-web-guidanceWhen an agent builds a dialog, form or scroll effect from memory, it can reach for an old pattern even when the platform has a native API. Modern Web Guidance is Google Chrome’s modern web guidance skill for coding agents. It directs the agent to search for one current HTML, CSS or browser-API pattern, retrieve the matching guide, then check the implementation against its recommendations and compatibility data. The repository README lists 250 covered web features; the 1.0 release was announced on November 10, 2026.
How the Modern Web Guidance skill works
Before writing or updating web UI, CSS or client-side JavaScript, the skill asks the agent to search with a short, action-oriented English query for one capability, such as “animate a dialog.” It discourages adding framework names, route names or several unrelated features to the query. Search returns guide IDs and descriptions. If the results are weak, the agent should try one more query using a concrete HTML element or UI primitive, then stop if no guide matches. It should retrieve relevant IDs directly instead of listing the whole catalog for every task.
A retrieved guide supplies implementation advice and any discipline-level guidance that applies, such as accessibility, performance, security or CSS. The agent then checks that it followed the guide’s fallback requirements. If the topic is not covered, it should continue without forcing an unrelated recommendation. This makes the skill useful for focused work such as choosing native dialog behavior or laying out a responsive table, while keeping the context focused on the feature being changed.
What the guides cover
The README groups its examples under user experience, CSS layout, performance, forms and UI, accessibility, and built-in browser AI. The catalog includes topics such as container queries, Popover, View Transitions, passkeys, image priority and Interaction to Next Paint diagnostics. The README says the guides are designed to be token-efficient, and each one serves a specific task. The source repository contains the authoring, calibration and evaluation work; the consumer-facing skill and npm CLI are distributed in GoogleChrome/modern-web-guidance. The README says the project is stewarded by Chrome, Edge, Firefox and MDN teams alongside the web development community.
Compatibility, network and privacy
The compatibility rule is unusually explicit: features marked Baseline Widely Available can be used without a fallback by default. For a feature outside that status, the agent must follow the guide’s fallback recommendation unless the user has supplied a different browser policy. The guides are organized by topic, including HTML, CSS, JavaScript, forms, accessibility, performance and PWAs. Teams that do not want fallback code should define a browser policy before asking agents to use newer APIs.
The npm package metadata requires Node.js 22.0 or newer. Installing or updating the package needs network access; the skill does not ask users for a model API key. The project’s README discloses default anonymous telemetry. The source code logs the CLI search query, returned guide IDs, operating system, CLI and skill versions, agent name, a latency bucket and success status to Google from a detached background process; the README says raw user prompts are not collected. Set DISABLE_TELEMETRY=1 in the shell environment to opt out. This is useful for a team that wants a consistent compatibility check, but the telemetry setting deserves a look before the CLI becomes a standard dependency. It suits frontend teams that need current platform practice and explicit compatibility limits; backend, build-script or test-config work falls outside its triggers.
As of November 12, 2026, the distribution repository showed 4,414 stars and the TypeScript source repository showed 1,537; both report Apache-2.0. I’d use this when an agent is changing browser-facing behavior and current platform guidance matters. For an agent that needs to establish product audience, visual direction and design tokens first, frontend-design handles that neighboring design problem; Modern Web Guidance focuses on browser capabilities and compatibility. For broad legacy modernization, its legacy-scan can only check about one fifth of the guide corpus, so a clean scan is not proof that a whole application follows every guide. This entry is based on the repositories’ READMEs, SKILL.md and telemetry source; the CLI was not run here.