← ClaudeAtlas

designlisted

Design UI that doesn't exist yet: visual direction, profile (dense tool vs marketing/consumer) and optional style (minimal, premium, brutalist, cinematic, playful, technical, glass), tokens, color, type, spacing, elevation, motion, dark mode, and DESIGN.md. Use when building a new page, screen, or project from scratch (landing, pricing, dashboard, app shell), setting up or reworking Tailwind or CSS-variable tokens and themes, building from a design file, adding dark mode (also to an existing project), or when the user asks for a visual direction or a named style ("thiết kế giao diện", "làm trang landing", "dựng màn hình mới", "thêm dark mode"). For a screen that already exists, use restyle (keep the layout, remove the generated look) or redesign (new visual language on existing content). Not for component behavior and states (see ui-interaction).
viettdann/arclight-kit · ★ 0 · Web & Frontend · score 65
Install: claude install-skill viettdann/arclight-kit
# Design Without an explicit direction, generated UI falls back to framework defaults (Tailwind indigo and zinc, Inter, the default shadcn theme, a gradient blob behind the hero), so every project looks the same. This skill makes the visual decisions explicit and keeps later work consistent with them. ## Match the effort to the task - **Small change** (tweak a component, add a button or column, adjust spacing): use the tokens and the shared components already in the code. Skip `DESIGN.md`, profile and style references, and questions. Check contrast only for color pairs you introduced. - **New surface or token work** (new page or screen, new project, setting up or reworking tokens or themes, or the user asks for a direction): follow the workflow below. A change inside an existing surface (a new section, a modal) is a small change if it uses only existing tokens; if it needs a color, font, or scale value the tokens don't have, it's token work. ## Sources The brief decides what to build; the code decides only which values to reuse. Carry over only what the user names. - **Read:** the brief and the skill's arguments, `DESIGN.md`, token and theme files (Tailwind config or `@theme`, CSS variables), the component library and shared primitives, all in the current working tree. - **Don't read** unless the user names the exact source in this conversation: git history (`git log`, `git show`, `git diff` against old commits), other branches, stashes, other repos, worktrees, or sibl