- Chrome's preview Modern Web Guidance gives coding agents advice on browser features. The team says models repeat old habits learned from legacy code.
- Developer Nolan Lawson says web components felt like an afterthought, with most material added in one commit about three weeks before his post. The sources give no Chrome response.
- Leaders should ask which guidance their agents load, who maintains it, and whether its telemetry is switched off.
The Chrome team says coding agents often default to older patterns, because their training data holds vast amounts of legacy code. That makes the guidance an agent loads worth attention. A Chrome project shows why.
What Chrome released
The Google Chrome team has published Modern Web Guidance as a preview. The Microsoft Edge team and the wider web community support it. It is a set of skills: packaged advice on web features and browser compatibility that coding agents can load. The aim is to steer agents away from legacy patterns.
The team explains its reason. Models learned from a huge pile of older code, so agents tend to repeat old habits. The team says this produces bloated JavaScript for jobs that browsers now do natively.
How it works
The skill includes a command-line tool. When an agent needs help, the tool sends short, focused guides into its context window. That is the text the agent holds in mind while it works. Topics include layout, forms, speed, passkey sign-in and on-device language features.
The team says it keeps the guides short on purpose. It runs tests and removes advice that models already know. It also says the npm package has no extra dependencies, which it links to low delay and supply-chain security.
The tool collects anonymous usage data. Google lists install counts, the agent's name, guide IDs and the search queries the agent writes. It says raw user prompts are not collected. Setting DISABLE_TELEMETRY=1 turns collection off.
One developer's reading of web components
Developer Nolan Lawson watched a demo and then read the code. He says web components felt like an afterthought. Web components are browser-built parts for reusable interface pieces.
Early on, he says, they were nearly absent. A single commit about three weeks before his post added material on them.
The repository now lists seven web-component guides. They cover custom elements, shadow DOM, styling, accessibility, form controls and server-rendering. Lawson says they mostly help people who already use web components.
He points to a section titled "Decide whether you even need a custom element". He says it sounds discouraging at times. He thinks an agent building a brand-new product with this guidance would probably not pick web components.
Those are his views, not Chrome's. The sources reviewed here contain no response from the Chrome team. Lawson also argues that web components add little for end users. He says compile-time CSS scoping gives the same speed gain as shadow DOM.
He names exceptions too. One line tells Chrome extension authors to use shadow DOM for complex interface injected into a page. He also mentions a line that points to web components for shared design systems, embedded widgets and self-contained interface parts.
The project's own web-components guide describes itself as the one to use for reusable components, design systems and server-rendered custom elements. Whether that adds up to a recommendation is a judgment call.
The idea behind the story
This shows where a technology choice can now be made. When a team uses an agent with this guidance, part of the decision happens in the guides its tool feeds into context before the agent writes code.
Those guides are editorial. Someone decides which features get a guide and how firmly each is advised. Here the process is public. Lawson could read the code and see when web components appeared.
Any guide reflects its authors' priorities. Chrome's stated priority is native browser features that it says are faster and more accessible. The project calls itself a preview and says it is still adding content.
Questions to put to your team
Ask whether your developers use agent guidance, and which packs they have installed. Find out who maintains each one and how often it changes. The Chrome team says it uses npx so content does not go stale. That also means the advice can change underneath you.
Ask whether telemetry is on. Search queries written by an agent could hint at what your team is building, even though raw prompts are not collected.
Ask for a review when guidance changes your standards. If an agent now picks native features over your framework, that is an architecture decision. It should have an owner.
The lesson is simple. In an agent-written web, the instructions behind the code carry more weight than any single line of it.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Google Chrome team (GoogleChrome/modern-web-guidance on GitHub).
