ui-design-guidancelisted

Canonical overlay for graphical UI or frontend redesign, polish-heavy implementation, and deep UX review; use `ui-guidance` for routine changes. Compose with matching implementation guidance when visual direction, accessibility, interaction, responsive behavior, forms, navigation, or data presentation need stronger discipline.
n-n-code/n-n-code-skills · ★ 4 · Web & Frontend · score 75

Install: claude install-skill n-n-code/n-n-code-skills

# UI Design Guidance This is a composable overlay, not a standalone workflow. Use alongside the repo's implementation skill when the change touches graphical UI or web frontend code. This is the stronger UI overlay in this repo. Prefer it over `ui-guidance` when the task is redesign-heavy, polish-heavy, or needs explicit UX review beyond basic UI hygiene. Choose activity independently from visual direction. A review request is read-only unless the user also asks for remediation; preserve versus redesign describes the intended product direction, not permission to edit files. ## When to use - the repo includes graphical UI or web frontend code - the task asks for UI implementation, redesign, beautification, styling, or frontend polish - the task changes how a feature looks, feels, moves, or is interacted with - the work includes new pages, components, forms, navigation, responsive layout, animation, or charts/data display - the task asks for UX review or quality improvement, not just visual changes - the change touches web views, desktop UI, embedded panels, dashboards, pages, landing screens, or rendering layers ## Not for - terminal UIs; use the matching terminal-framework guidance - pure data visualization or plotting libraries without product-interface work - backend-only changes with no UI surface ## Core workflow 1. Read the touched UI files and nearby components first. 2. Choose the activity: - implementation when the user asks to build, change, redesig