Web Design Guidelines needs a fetch-capable agent
Checked 10 November 2026. The current Web Design Guidelines skill file still instructs the agent to fetch its current rules with WebFetch before reviewing the specified files. It contains no inline fallback. Without that fetch route, the published workflow cannot run as written.
A July 2026 issue reports one pilot in which an agent without WebFetch could not load the rules. The author scored five criteria on one React component and reported 4/5 with the skill and 2/5 without it. Those are one author's criteria on one planted-issue case, not a general improvement estimate. The issue is closed, but the current file still requires WebFetch. We did not run the skill.
Before reviewing UI files
- Name the files and verify that the agent can fetch the rules URL.
- Record the skill revision and the fetched rules revision.
- If fetch is unavailable, use an explicit local rules copy or a direct brief. Treat that as an adapted workflow, not proof that the published skill completed its review.
- Check any reported finding against the actual UI state; file review is not a full accessibility or rendered-flow test.
The recommendation remains conditional. No paired result test by this catalogue shows that this skill beats a direct review brief.