cupertino-ui-consistency

Maintain Cupertino + Lumina visual consistency for the AERA frontend. Use when creating or modifying UI, CSS/tokens, layouts, components, menus/overlays, tables, charts, or interaction states in this repo.

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

When & Why to Use This Skill

This Claude skill is engineered to maintain visual and functional consistency across the AERA frontend by blending Cupertino-inspired design principles with the Lumina framework. It provides a rigorous set of guidelines and automated checks for design tokens, CSS styling, and component architecture, ensuring a premium, glass-morphic aesthetic while upholding strict accessibility and interaction standards.

Use Cases

  • Standardizing UI Components: Apply consistent 'glass' materials, squircle radii, and SF Pro typography to new or existing frontend elements to ensure a cohesive user experience.
  • Design Token Management: Define and enforce a unified palette, spacing scale, and motion tokens to prevent visual regression and maintain brand integrity within the codebase.
  • Accessibility & Interaction Audits: Automatically verify that interactive elements like menus, popovers, and overlays meet WCAG AA standards and support full keyboard navigation.
  • Refining Data Visualizations: Optimize the presentation of complex tables and charts using tabular numerals and minimal grid lines for a clean, professional, and readable look.
namecupertino-ui-consistency
descriptionMaintain Cupertino + Lumina visual consistency for the AERA frontend. Use when creating or modifying UI, CSS/tokens, layouts, components, menus/overlays, tables, charts, or interaction states in this repo.

Cupertino Ui Consistency

Overview

Apply a consistent Cupertino-inspired layer on top of Lumina: clean, recessed surfaces, glass materials, soft shadows, and restrained hierarchy. Use the checklist to align typography, tokens, components, interactions, and accessibility.

Workflow

  1. Define and use tokens first (palette, type, spacing, radii, elevation, motion).
  2. Restyle components to match Cupertino + Lumina (materials, shapes, states).
  3. Validate interaction completeness and accessibility (keyboard, focus, reduced motion).

Checklist

  • Typography: SF Pro Display/Inter system stack; avoid custom licensed fonts; set font-variant-numeric: tabular-nums for numbers.
  • Tokens: define palette (single blue, no purple), desaturated red, radii (squircle), shadows, elevation, spacing scale, type scale, icon sizes, and motion tokens.
  • Materials: apply glass/blur for sidebar, popovers, dropdowns, sticky headers; keep soft ambient shadows.
  • Components: ensure hover/active/focus-visible/disabled/loading/error states; keep weights light and rely on color/spacing.
  • Overlay behavior: Esc closes, click-outside closes, focus returns to trigger, viewport-safe positioning.
  • Keyboard nav: arrow keys for menus, enter/esc actions, tab order for all controls.
  • Motion: Apple-like easing; 150-250ms; opacity/transform only; reduced-motion safe.
  • Tables: text left, numbers right, dates centered; no vertical borders; subtle row hover and minimal sort indicators.
  • Charts: minimal axes and grid; subtle hover tooltips; tabular numerals in labels.
  • Forms/settings: System Settings layout with grouped sections; inspector panel or modal for edits.
  • Sidebar: narrow, translucent, pill active state, subtle divider for secondary/profile items.
  • Menus/dropdowns/popovers: frosted, soft shadow, consistent radius, subtle separators, full keyboard support.
  • Accessibility: WCAG AA contrast, visible focus, keyboard access for all interactive elements.
  • Iconography: monoline SF Symbols-like look; consistent stroke weight and sizes.

Validation

Confirm tokens are used across components, overlays meet interaction rules, and UI changes keep the Lumina aesthetic while applying Cupertino polish.