← ClaudeAtlas

product-ui-designlisted

Build functional product UI — dashboards, SaaS tools, settings, app screens, admin panels, data tables, forms — that looks like a real shipped product (Apple / Linear / shadcn register), not generic AI slop. Enforces restraint, kills AI-tell signals (glowing status dots, mono eyebrow labels, purple-blue accents, filled+ghost hero button pairs, four-cell stat strips), and grounds choices in observation of real products. Use when the user asks for product/app/dashboard/admin/internal-tool UI. For expressive marketing or landing-page aesthetics, use frontend-design instead.
kuras3/product-ui-design · ★ 0 · Web & Frontend · score 72
Install: claude install-skill kuras3/product-ui-design
# Product UI without the AI tells This skill builds **restrained, production-grade product UI**: the register of Apple, Linear, Stripe dashboard, shadcn/ui, Vercel, GitHub, Notion — interfaces that look like a real team shipped them. It is the counterpart to maximalist marketing design. The goal is not to be unforgettable; it is to be **correct, calm, and free of the signals that mark a UI as AI-generated**. AI models, left to default, converge on a recognizable "slop" look for product UI: purple-blue gradients, glowing status dots, mono labels used as decoration, evenly-timid palettes, four identical stat cells, a filled+ghost button pair in every hero. This skill prevents that by combining three disciplines: **observe before you invent**, **a two-layer floor/ceiling model**, and **output-time hard-checks** against a list of known tells. ## When to use / when NOT to use - **Use this skill** for functional/product UI where looking *shipped and trustworthy* matters more than looking *expressive*: dashboards, SaaS app screens, settings, admin panels, data tables, forms, internal tools, B2B. - **Do NOT use this skill** for expressive marketing pages, brand/landing heroes, campaign sites, or anything whose job is to be a memorable artifact — that is a different register (commit boldly, distinctive type, atmosphere). Use a marketing/expressive-design skill instead (e.g. `frontend-design`). - **vs a generalist UI skill** (e.g. `ui-ux-pro-max`): use this one when the priority is