Get Design

Overview

Run a product-grounded UI design workflow. The goal is not merely polished CSS: it is an interface with a clear job, a recognizable visual point of view, content that carries the design, hierarchy that reflects user priorities, and interaction states that work in the real usage scene.

This skill is a native Viserys adaptation of the Impeccable design playbook and anti-slop catalog. It contains no runtime dependency on Impeccable, its CLI, hooks, binaries, or external detector. The rulebook is advisory evidence; a deliberate choice can override a default when the product brief, brand, platform, or accessibility requirement earns it.

When to Use

• Creating a new page, screen, component, landing page, dashboard, checkout, settings flow, docs surface, portfolio, or mobile UI.
• Redesigning an existing visual world rather than only fixing a local defect.
• Reviewing a UI that feels generic, templated, “AI-generated”, or disconnected from its product.
• Improving hierarchy, layout, spacing, typography, color, imagery, motion, copy, responsive behavior, states, or design-system consistency.
• Auditing a rendered interface for usability, accessibility, performance, responsive behavior, or implementation integrity.
• Documenting or extracting an existing design system.

When NOT to use: Use frontend-ui-engineering for component architecture, state management, semantic implementation, and accessibility mechanics when visual direction is already settled. Use performance-optimization for non-visual performance work.