When should you use it?
- Your agent keeps adding a JavaScript library for things the browser can now do on its own, such as modals, popovers or auto-growing text boxes
- An agency or in-house team ships client websites with coding agents and wants consistent, accessible front-end code
- You inherited an older site and want a list of patterns worth modernizing before a redesign
Not for: Back-end, database or infrastructure work; the skill is meant to stay quiet for those tasks; Environments without network access, unless you can allow the package download once; Teams that must support very old browsers and cannot ship any fallback code
What do you need, and what do you get?
You need
- A coding agent that reads SKILL.md files (or installs plugins from the repository)
- Node.js with npx or pnpx, and permission for the agent to run the modern-web-guidance package
- Optionally, a written browser support policy in your AGENTS.md or CLAUDE.md file
You get
- Front-end changes built on native HTML, CSS and browser APIs where they fit
- Fallbacks added only for features that are not yet widely supported
- A short note at the end of each change naming the guides the agent relied on
- On request, a scan report of legacy patterns in an existing project
How does it work, step by step?
- Install the skillAdd the plugin or copy the skills folder from the GoogleChrome repository into your agent's skills directory.
- Allow the lookup toolApprove the agent to run the modern-web-guidance package through npx, scoped to that package only rather than to any npx command.
- Write a support policyAdd a line to AGENTS.md or CLAUDE.md saying which browsers you support and how much fallback code you accept.
- Build as usualAsk for front-end work in plain words. The agent searches the guides first, then writes the code and lists the guides it used.
- Audit older code on purposeWhen you want modernization, ask explicitly for a legacy scan of a folder, review the findings, then let the agent fix the ones you approve.
The prompt
Our adapted version, written to work in Claude Code, Microsoft Copilot and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Before you write any HTML, CSS or browser JavaScript for this task, check the modern-web-guidance skill for the pattern involved: {feature}. Our browser support policy: {support_policy}. Prefer built-in browser features over new libraries, add fallbacks only where the policy requires them, and do not touch back-end files. When you finish, list each guide you used and the specific choice it changed in one sentence each. If no guide applied, say which ones you checked.
The original skill is published by GoogleChrome on GitHub (GoogleChrome/modern-web-guidance). Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- The skill depends on downloading a package at run time. In locked-down sandboxes, approve network access for it before the first task or it will stall.
- Native features still need testing in the browsers your customers use. Treat the guides as strong defaults, not a replacement for QA.
- Asking for a full legacy scan on a large repository can produce many findings at once. Work through them in small batches.
- Granting broad npx permission to make setup easier is risky. Allow only this one package.
Our take
Anyone who has reviewed front-end code from a coding agent has seen the pattern: it reaches for the approach that was popular years ago because that is what most of its training examples show. This project attacks the problem at the source, by giving the agent a current reference and making it look things up before it writes. We like three design choices. The guides are written by people, not generated. The lookup happens locally and returns only what is relevant, so it does not crowd out your own instructions. And each change ends with a short note on which guides were used, which makes review easier. For agencies building small business websites, this is a cheap way to get more accessible pages and fewer dependencies without retraining anyone. Our cautions are practical. It needs a package download at run time, which some sandboxes block, and you should scope the permission to this one tool. In our dry run, an agent asked for a delete confirmation box chose the native dialog element over a modal library and named the guide it followed.
Where the time goes back: Code that uses what the browser already provides needs fewer libraries, less custom JavaScript and fewer accessibility fixes later, so reviews and maintenance get shorter.
FAQ
Who maintains it?
Does it fill up my agent's context?
Does it work with React or other frameworks?
Source and credit
This playbook is based on work by GoogleChrome. We summarize it and link to it and write our own adapted prompt.
- Original
- modern-web-guidance skill (GoogleChrome/modern-web-guidance)
- Creator
- GoogleChrome
- Published on
- GitHub (GoogleChrome/modern-web-guidance)
- Original date
- Nov 10, 2026
- License
- Apache-2.0
- Originally for
- Custom agent
- AI dry run
- Nov 11, 2026: passed. Dry-run tested by our AI test agent on sample input. Native dialog chosen over a library, policy respected, guide named in the closing note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 11, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under Apache-2.0 by GoogleChrome. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.
Are you the creator? Claim or correct this page.