Google's web skill tells coding agents to stop cluttering pages

Modern Web Guidance’s November 2 GitHub release adds a direct brief for coding agents: put the content first and reduce interface noise. Version 0.0.197 introduces a guide addressing intrusive overlays, oversized persistent bars and secondary controls that crowd the page.

The new guide recommends avoiding unsolicited newsletter modals, reserving space for media before it loads, keeping persistent bars compact and using popovers or expandable details for secondary material. Its scroll-direction example keeps navigation visible while it contains keyboard focus. The guide also distinguishes limited browser support for scroll-state queries from more widely available behavior, with fallback examples rather than assuming one CSS feature works everywhere.

Other release changes address concrete mistakes agents can make. Inactive single-page-app views should use inert alongside hidden content so keyboard navigation does not reach them. Generated-content accessibility advice adds a fallback for older CSS parsers, and input-method guidance explains how composition events can otherwise trigger premature Enter submission.

This is a preview guidance pack for an existing coding agent, not a new model. Its README documents an interactive npx modern-web-guidance@latest install route and host integrations including Codex and Claude Code. Guide search runs locally without a model API key, according to the project. The README also discloses anonymous telemetry covering CLI search queries and guide retrieval, with DISABLE_TELEMETRY=1 as an opt-out; model usage costs and the host’s execution permissions remain separate.

The tagged README reports a 205-task evaluation snapshot in which Codex CLI with GPT-6.1 Sol moves from 55% unguided to 82% guided, and Claude Code with Opus 5.5 from 58% to 90%. These are project-reported suite results, not independent AITrending tests or an isolated measurement of the newly added guide.

Distribution has a qualification: the GitHub tag exists, but npm still returned 0.0.196 as latest during review, and the exact 0.0.197 npm lookup returned no version. The new tag’s metadata specifies Node 22 or newer and Apache 2.0 licensing. Readers should distinguish the published guidance update from a confirmed matching package rollout.