design-refinementlisted

<!-- Adapted (text only, no scripts) from Impeccable — https://github.com/pbakaus/impeccable — Apache-2.0, (c) 2025 Paul Bakaus; itself derived from Anthropic's frontend-design skill (Apache-2.0, (c) Anthropic) and ehmo/typecraft-guide-skill. Modified for the VibeGod Tech Team pipeline. --> # Design Refinement — distinctive, not generic The default output of an AI frontend is generic: a centered rounded card on a flat background, one timid accent, a system/Inter font, gentle whitespace. This skill exists to break that. Pairs with `frontend-craft` (the doctrine) and is run via `/polish`. User > skills > default. ## Fits in the pipeline Stage 6 (design + build) and a `/polish` pass at Stage 7 **before** the `ux-design-reviewer` visual gate. The designer/engineer run it; the reviewer then audits. ## The slop test (the bar) If someone could glance at it and say **"AI made that"** without hesitation, it failed. The target: a viewer asks *"how was this made?"*, never *"which AI made this?"* Restraint **without intent** now reads as mediocre, not refined. ## Pick the register first (brand vs product) - **Brand** (design IS the product: landing/marketing/portfolio/campaign): the bar is **distinctiveness** — POV, risk, committed scale, real imagery. Go big. - **Product** (design SERVES the product: app UI, dashboards, tools): the bar is **earned familiarity** — a fluent Linear/Figma/Notion/Raycast/Stripe user should trust it. Distinctive but calm; "bolder" = stron