← ClaudeAtlas

industry-design-directionlisted

Pick a concrete visual direction for a website or app in a specific industry — which aesthetic, which palette, which font pairing, which page structure — from a library of 95 industry profiles, 57 defined styles, 96 palettes, 57 font pairings, and 30 landing structures. Trigger for "design a landing page for a dental clinic", "帮我设计一个餐厅网站", "what should a fintech app look like", "给这个 SaaS 产品定一套 配色和字体", "我要做一个电商网站,用什么风格", or whenever someone needs a starting direction for a product whose industry is known but whose look is not. Do NOT trigger once a direction already exists and the job is enforcing it across screens (use `ui-design-system` — that skill operationalizes a chosen aesthetic into tokens; this one chooses it). Do NOT trigger for dense dashboards/terminals (`terminal-software-design`), chat interfaces (`conversational-ui-restraint`), or trading-app components (`trading-ui-patterns`) — those are category skills with far more depth for their category than the one-line profile here. Portable: every refer
artherahq/skills · ★ 2 · Web & Frontend · score 68
Install: claude install-skill artherahq/skills
# Industry design direction Most generated UI looks templated because the aesthetic was never actually chosen — it defaulted. Purple-blue gradient, glassmorphic cards, Inter everywhere, hero-features-CTA. That default is applied identically to a dental clinic, a metal fabricator, and an NFT marketplace, and it is wrong for all three in different ways. This skill exists to make the choice explicit and industry-grounded, before any component is written. It is the *exploration* step. Once a direction is picked, `ui-design-system` turns it into enforceable tokens. ## The five decisions, in this order Order matters — each one constrains the next, and taking them out of order is how you end up retrofitting a palette onto a layout that fights it. 1. **Industry profile** → `references/industry_profiles.md` Find the row matching the product. Match on the profile name *or* its keywords: users describe products in their own words ("clinic booking site"), not in the library's labels ("Healthcare App"). This gives you the primary style, viable alternates, the page structure, and — the part most worth reading — the constraint that industry most often gets wrong. 2. **What that style actually is** → `references/style_library.md` The profile *names* a style; this defines it — colors, effects, theme support, performance, the CSS that produces it, and a done-checklist. Read the **"Do NOT use for"** line before the "Best for" line: a style applied to the case it