graphic-ux-ui-design

Applies evidence-based UX/UI design standards for interfaces, accessibility, and design systems.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill graphic-ux-ui-design-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphic-ux-ui-design
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/frontend-design/skills/graphic-ux-ui-design
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill graphic-ux-ui-design-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design decisions are often based on myths or trends rather than evidence, leading to inaccessible interfaces, inconsistent design systems, and usability failures like low-contrast text and missing form labels. ## Core Features & Use Cases - Visual Design Standards: Provides concrete rules for color token architecture, WCAG contrast ratios, dark mode surfaces, typography (66ch line length), and 8pt grid layouts. - Component Pattern Guidance: Covers evidence-based choices for navigation, forms, buttons, modals, loading states, and list pagination patterns. - Accessibility & Design Systems: Details WCAG 2.2 requirements, semantic HTML practices, screen reader testing, three-tier token architecture, governance models, and SemVer versioning. - Use Case: When auditing a web app for accessibility, use this Skill to identify the six most common WCAG failures and get staged remediation steps with exact contrast ratios and touch target sizes. ## Quick Start Review my landing page design for accessibility issues and recommend fixes based on WCAG 2.2 AA standards.

Frequently Asked Questions about graphic-ux-ui-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my website WCAG 2.2 compliant?

WCAG 2.2 AA compliance requires 4.5:1 contrast for normal text, 24x24 CSS px minimum target sizes, visible focus indicators, and single-pointer alternatives for drag interactions. Start by fixing the six most common failures: low contrast, missing alt text, missing form labels, empty links, empty buttons, and missing document language.

What is the best color contrast ratio for accessibility?

WCAG AA requires 4.5:1 for normal text, 3:1 for large text (24px or 18.7px bold), and 3:1 for non-text UI elements. AAA raises these to 7:1 and 4.5:1 but is aspirational. Use APCA as a supplementary check, especially for dark themes.

Should I use infinite scroll or pagination for product lists?

Use Load More with lazy-loading as the default for most product lists, pagination for goal-driven lookup and SEO, and infinite scroll only for exploratory feeds like image galleries. Baymard research shows infinite scroll harms goal-driven search because users lose their place and cannot bookmark results.

How do I structure design tokens for dark mode support?

Use a three-tier token architecture: primitive tokens hold raw values, semantic tokens encode intent like color-action-primary, and component tokens scope to specific elements. Applications consume semantic tokens, so dark mode becomes a matter of re-pointing tokens rather than editing components.

Why should I avoid pure black backgrounds in dark mode?

Pure black (#000000) causes halation and blooming effects and disables shadow perception. Material Design recommends #121212 as the base surface, expressing elevation through lightness steps of roughly 3-5 points between layers instead of shadows.

When should I use ARIA attributes versus semantic HTML?

Use native HTML elements first since they carry built-in roles, keyboard handling, and focus management. WebAIM data shows pages with ARIA average 34-41% more detected errors than pages without. Reserve ARIA for genuinely custom widgets like tabs, comboboxes, and live regions.