ui-ux-patterns

When designing layouts, navigation, forms, or feedback components. Reference for consistent UI decisions.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill serves as a comprehensive UI/UX design reference and quality assurance tool. It provides standardized patterns for layouts, navigation, forms, and feedback components to ensure consistent, user-friendly interface decisions. By integrating industry-standard heuristics and a rigorous verification checklist, it helps developers and designers avoid common anti-patterns and maintain high-quality design standards across web and mobile applications.

Use Cases

  • Standardizing Interface States: Ensuring every screen defines the four essential states (Loading, Empty, Error, and Success) to improve user retention and clarity.
  • Form UX Optimization: Applying best practices for input validation, error messaging, and multi-step progress indicators to reduce user friction and abandonment.
  • Design System Implementation: Establishing a clear action hierarchy and consistent feedback mechanisms (Toasts, Modals, Spinners) based on established UI patterns.
  • Mobile-First Accessibility Audits: Using the verification checklist to ensure touch targets meet the ≥44px standard and that mobile breakpoints are correctly defined.
  • UI/UX Code Reviews: Referencing the anti-patterns guide during code reviews to catch issues like 'walls of text' or non-critical modal usage before deployment.
nameui-ux-patterns
descriptionWhen designing layouts, navigation, forms, or feedback components. Reference for consistent UI decisions.
version1.0.0
tokens~550
confidencehigh
- https//lawsofux.com/
last_validated2025-01-10
next_review2025-01-24
tags[ui, ux, design, frontend]

When to Use

When designing layouts, navigation, forms, or feedback components. Reference for consistent UI decisions.

Patterns

4 Required Screen States

Every screen MUST define:

  1. Loading - skeleton or spinner
  2. Empty - illustration + CTA
  3. Error - message + recovery action
  4. Success - content + next steps

Layout Patterns

Card Grid     - Products, dashboard widgets
Master-Detail - Email client, settings
Split View    - Editor + preview

Form Best Practices

- Validate on blur (not on every keystroke)
- Error message below field (not tooltip)
- Color + icon for status (not color alone)
- Multi-step: max 5-7 steps, progress indicator

Feedback Patterns

Toast         - Auto-dismiss 3-5s, non-blocking, offer Undo
Modal         - Destructive actions, critical decisions only
Loading       - Skeleton (<3s), Spinner (unknown), Progress (>5s)

Action Hierarchy

Primary   - Right side, filled button, max 1 per view
Secondary - Left of primary, outline button
Danger    - Red outline (not filled), requires confirmation

Anti-Patterns

  • Skipping empty/error states
  • Walls of text (use scannable content)
  • Desktop-only thinking (mobile-first!)
  • Modal for non-critical info (use toast)
  • Tiny touch targets (<44px)

Verification Checklist

  • All 4 states defined (loading, empty, error, success)
  • Touch targets ≥44x44px
  • Mobile breakpoints defined
  • One primary action per view
  • Destructive actions require confirmation
  • Feedback is immediate and clear