ui-and-accessibility

What problem does it solve?

This Skill eliminates the risk of costly, unreviewable sweeping UI redesigns — the single most expensive failure mode in this project's history — and ensures all visual changes meet the project's strict WCAG 2.1 AA accessibility standards without re-deriving patterns from scratch.

Core Features & Use Cases

• Strict change scoping rules: Enforces one widget or screen per PR and separates restyle work from restructure work to keep diffs small, reviewable, and revertible.
• Shared widget reuse table: Curated list of existing Flutter widgets to use instead of building duplicate components, reducing maintenance burden for the solo maintainer.
• WCAG 2.1 AA accessibility catalogue: Verified semantics patterns for all interactive elements, including toggle buttons, filter chips, star ratings, and tappable cards, to ensure screen reader compatibility.
• Preserved screen invariants: Enforces critical fixed patterns like the festival-flash guard, four-signal loading/error UI, and navigation helpers to avoid regressing resolved bugs.
• Use Case: If you need to add a "Tasted" status badge to the drink card, this skill guides you to scope the change to a single restyle PR, use the existing DrinkCard widget, follow state-aware semantics labeling, and update golden files deliberately to avoid unintended visual drift.

Quick Start

Load this skill before making any visual changes to Flutter screens, widgets, themes, or accessibility features in the Cambridge Beer Festival app.