Chrome's Modern Web Guidance Shoves Curated Best Practices Into AI Coding Agents
Most AI coding agents generate stale, over-engineered frontend code; this Skill gives teams a way to push current browser APIs and safety practices into agent context without modifying the model. The built-in evaluation pipeline sets a precedent for measuring whether a Skill actually improves output, which is rare in the agent-plugin ecosystem.
AI-generated frontend code tends to look dated because training data has far more old patterns than new ones. Modern Web Guidance attacks that at the context level: a Skill that feeds agents curated guides on web platform features, best practices, and compatibility data. It works through a two-step retrieval: an offline `search` using a zero-dependency embedding model plus BM25 to match natural-language queries to the most relevant guide, then a `retrieve` step that pulls the full guide into the agent's context. The package is self-contained with no network or API key needed, and uses `npx` so content stays fresh.
The project ships with a closed-loop evaluation pipeline. Experts write guides, then the repo auto-generates tasks, golden solutions, and Playwright scoring scripts. Scoring scripts must pass 100% on the golden solution and fail 100% on the unmodified base app to be accepted. Agents then run tasks with and without guidance to measure uplift. Official results from November 8 show improvement of +36 points for antigravity_cli (58% to 94%), +31 for claude_code (57% to 88%), and +28 for codex_cli (54% to 82%). Those numbers are the project's own evals, not a third-party benchmark, and cover 250 web features and 203 scenarios across 18 categories.
The evaluation pipeline is the most valuable part: it treats a Skill like a testable artifact, with pass/fail gates on golden solutions and base apps, which makes the claim "this Skill helps" falsifiable rather than marketing.
Gating unstable features behind explicit developer consent is a pragmatic compromise between giving agents the newest APIs and protecting against compatibility breakage; it puts the risk decision back on the developer.
The +27 to +36 point uplift numbers are only valid for the project's own tasks and scoring scripts; real-world business code may not see the same improvement, especially for scenarios outside the 203 covered.
Shipping a 250-feature guide set as a self-contained offline npm package shows a deliberate choice for supply-chain security and low latency, trading off the ability to fetch live docs for reproducibility.