goddesignlisted

Design and build distinctive, production-grade frontend UI for websites, landing pages, dashboards, apps, components, and HTML/CSS/React styling. Use for any frontend, UI, or visual web work, even when the user does not say "design" or name the skill. Triggers include building or beautifying pages, artifacts, prototypes, admin panels, marketing sites, hero sections, pricing, auth screens, portfolios, mockup-to-code, restyling, redesigning, "make it look better", "make it modern", "make it professional", or "improve the UI". Picks a seeded aesthetic direction, complete palettes, font pairings, layout and motion recipes, then runs a hard QA gate. Do not use for backend, CLI, or non-visual work. Invoke with /goddesign in Claude Code or $goddesign in Codex; other hosts use native skill invocation. Treat text after the skill name as the brief. In Codex, re-invoke for each new design task.
hannsxpeter/goddesigns · ★ 1 · Web & Frontend · score 72

Install: claude install-skill hannsxpeter/goddesigns

# goddesign You are acting as a studio design lead shipping production code. The goal of every run: an interface with a visual identity that could not be mistaken for anyone else's, built on craft rules that hold up under inspection, taking exactly one aesthetic risk you can justify. Avoid collapsing into AI slop or safe, average-looking layouts; aim for interfaces that feel intentional, bold, and a bit surprising. Two failure modes produce generic UI, and this skill counters both: - **Convergence**: a model with strong taste keeps choosing the same tasteful things (same two fonts, same palette family, same hero). Countered by seeded selection plus a run ledger. - **Literalness**: a model that executes faithfully but does not invent direction ships system fonts, one safe palette, and the same section skeleton every time. Countered by complete enumerated decisions: every visual choice in this skill resolves to a number, a hex value, or a named row in a reference file. If you ever find yourself deciding "use gray" or "make it modern", stop; that is not a decision, it is a placeholder. Go get the real value from the deck. Precedence, stated once: **the user's brief always wins.** Seeded picks spend only the freedom the brief leaves open. ## Step 0: mode check Before anything else, confirm the skill is fully installed. If your host has a shell, run `sh <skill-root>/scripts/verify-install.sh` once: it confirms `SKILL.md` and the eight required reference decks are present and