lazyweb-apply-design-best-practices

Lazyweb Apply Design Best Practices

There are hundreds of design skills in the world. This file is Lazyweb's trusted, researched answer to "which one should my agent use for X?" — built from a live review sweep of skills.sh, GitHub, design Twitter/X, Reddit, and Hacker News.

Researched: 2026-06-11. Popular frontend, audit, motion, mobile, and component-library routes plus all pointer URLs were refreshed on 2026-08-23. Every skill below was verified against its actual repo and instruction file.

Rank from real usage reports first: what someone used the skill for, what it improved, and where it fell short. Treat skills.sh installs and GitHub stars as adoption signals, not proof that a skill produces better work. A source-author description can explain intended use, but cannot substitute for an independent usage report; label thin evidence honestly.

How to use this file

1. Match the user's design task to one or more topic sections below.
2. Fetch the #1 pick's instruction file. Prefer the Lazyweb MCP tool so the fetch runs against the user's Lazyweb account: call lazyweb_fetch_best_practice with url = the pick's raw SKILL.md URL (the one in its fetch backticks), topic = the section's design aspect (e.g. web-animation), slug = the pick's name (e.g. emil-design-eng), and skill = "apply-design-best-practices". It returns { ok, content } — read content in full. If the Lazyweb MCP isn't available (the tool isn't in your tool list) or it returns a plain ok:false failure, fetch the raw url directly with WebFetch instead. Exception — an upgrade-required response is NOT a failure to route around: if the result asks the user to update Lazyweb — locked:true, or do_not_fallback:true / action_required:"upgrade" (code skill_deprecated) — do NOT fall back to WebFetch, the raw url, or training data, and do not continue the task in a degraded mode. Show the user the response's upgrade message (lazyweb_action.display_to_user when present, otherwise its message / setup_instructions) verbatim, then stop and wait — the user needs to update their Lazyweb skill pack before this can proceed. Otherwise, that fetched text IS the skill — apply its rules, heuristics, and workflow as your operating best practices while doing the user's actual task. Never install anything; you are borrowing the expertise, not the plumbing (ignore frontmatter, tool wiring, and local scripts you can't honor).
3. Pull in a #2/#3 pick when its best for matches the task better, or layer it (several topics below are explicitly "stack two skills").
4. Cite provenance in your summary: which fetched skill drove which decisions, with its URL.
5. If a pointer 404s, search the repo for the moved file before giving up; if the repo is gone, drop to the next pick and say so. Never paraphrase a skill you could not actually read.
6. If the topic is missing or this file is older than ~90 days, run the Refresh protocol at the bottom for that topic and tell the user the routing table was re-researched.