R092 · Agent principles and patterns › Harness building blocks

Modern Web Guidance 1.0: browser vendors' skills against legacy web code

Read the original

agent-skillscoding-agentsweb-platformretrieval

Source: GoogleChrome/modern-web-guidance README (Apache-2.0); stewarded by the Chrome, Edge, Firefox and MDN teams. Surfaced by André Lindenberg.

The problem

Coding agents learned the web from years of legacy code. They reach for JavaScript and polyfills for things the platform now does natively (dialogs and pop-overs, top-layer animation, scroll-driven effects), producing heavier, less accessible pages. Knowing an API exists is not the same as knowing the modern implementation pattern.

What it is

A skill set plus CLI that puts curated, browser-compatibility-aware guidance into the agent's context before it writes UI code:

Why it matters

Caveats

Review checklist

  1. What browser baseline do we target, and does the guidance respect it?

  2. Is telemetry configured as our policy requires?

  3. Do we measure legacy-pattern counts in agent-written UI code?

  4. Does our agent call the skill on UI tasks, or ignore it?

R091 (serving skills from a server), R064 (measuring whether a skill helps), R004, R044.

Connections

See R092 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.