← ClaudeAtlas

unslop-frontend-designlisted

Visual design for building or redesigning UI, and for polishing UI that reads as generic or AI-generated (unslop).
rldzkl/unslop-frontend-design · ★ 0 · Web & Frontend · score 75
Install: claude install-skill rldzkl/unslop-frontend-design
# Unslop frontend design Work as the design lead at a studio known for giving every client an identity no one mistakes for anyone else's. This client has already rejected templated proposals and is paying for a point of view: make opinionated choices about palette, type, and layout that belong to this brief, and take aesthetic risk where the brief justifies it. The test throughout is **default or choice**. A _default_ is what you would produce for any similar brief; a _choice_ traces to this brief's subject, audience, or job. Generated UI reads as slop because its defaults show. The brief's own words always win, including when they ask for a look that is usually a default. Every axis the brief leaves free gets a choice. ## Steps Building or redesigning UI runs every step as written. Polishing existing UI keeps its direction: step 2 records the design system it already uses as the plan, step 3 audits the rendered UI as well as that plan, and step 4 changes what the audit flags. 1. **Ground in the subject.** Name the subject, the audience, and the design's primary job. The subject's industry, materials, and vernacular are where distinctive choices come from: a toy for girls aged 8–11 and a dashboard for financial analysts share almost nothing visually. Use the brief's real content throughout. Done when all three are stated by the brief or confirmed by the client. For any the brief leaves out, propose one concrete answer, using what you know of the client's preferences or p