Frontier models often default to legacy patterns for web development. For example, they prefer a JavaScript animation library over CSS scroll-driven animations, or build complex nested div monsters […] for customizable dropdowns.
Modern Web Guidance fixes that by injecting concise, task-scoped guides based on your prompt.
An interesting project offering coding agents access to a suite of best practice project guides. It’s by the Chrome team, but apparently now also has other browser manufacturers on board.
I haven’t yet tried it but I got a good flavour for how it works from Ahmad Alfy’s excellent review.
I’m encouraged by it having experts (area tech leads) like Lea Verou writing guides (Lea wrote the guide on dark mode).
I’m also interested in how they’ve set up their evals – which, they say, offer ongoing checks and proof that coding agents return better results when using Modern Web Guidance than not.
These kind of AI-related developments stir a bunch of emotions.
From one perspective this is a technological advancement – the ability to plug in expert guidance while you go faster, like Neo in the Matrix.
I like that the advice comes from experts who have been commissioned and paid, rather than just scraped from the web without permission.
There is also the small chance that the advent of AI might boost the application of web standards and best practices, if initiatives like this work and become used by big players. I’d prefer if people valued the good practices enough to resource and apply them regardless of using AI or not. Getting wins by the back door from use of resource-hungry AI feels similarly bittersweet to only being able to get accessibility wins as a by-product of some other exercise.
Inevitably, if you’ve been doing web development for a long time, a project like this also causes you to worry about your worth. For me, knowing and applying web good practices has been an important part of my career identity, and now that kind of knowledge is just a prompt away. This might be an unfounded concern; it might be one of those “your knowledge is still important; it’s just that you’re now directing rather than writing” situations. Which then begs the question of what that means for juniors who don’t yet have that knowledge.
Anyway, I’ll look to try it out soon. Perhaps I should recommend that the wider engineering department at work try it out, too.