← ClaudeAtlas

web-designlisted

Design product-specific web UI, responsive layouts and motion; keep the direction in DESIGN.md. Use for new pages, redesigns, generic-looking UI, janky animation, awkward phone behavior or layouts stressed by long or empty data.
ADWilkinson/astack · ★ 1 · Web & Frontend · score 74
Install: claude install-skill ADWilkinson/astack
# Web design Generated UI fails in predictable ways: the same fonts, the same violet gradient, cards inside cards, a centred hero with three icon tiles, decoration standing in for a point of view. This skill replaces defaults with decisions, then checks the rendered result. `<skill-dir>` below means this skill's own folder. Run its scripts from the project root so output lands in the project, not in the installed skill. ## 1. Load or create the design context Look for `DESIGN.md` (also `docs/DESIGN.md`, `BRAND.md`). If it exists, read it before touching UI; its tokens and rules win over your taste. If it does not exist and the work is more than a small fix, create one from [the template](references/design-md-template.md) by reading the code: real tokens from the CSS/Tailwind config, real fonts, real components. Mark anything you inferred as inferred. Update DESIGN.md when a session makes a durable decision (a new token, a rejected direction and why). This is how the next session avoids regressing to defaults. When the user corrects the same thing twice, or asks you to remember design feedback, turn the corrections into rules with [keeping the user's taste](references/taste.md): the user's words, a confirmed reason, and a check where code can enforce it. Before choosing HTML, CSS or browser JavaScript patterns, use [the web platform procedure](references/modern-web.md). It searches pinned guidance and checks browser compatibility while preserving the project’s components