fs-game-score

Classify, audit, and author files in docs/ against the Diátaxis framework (tutorial / how-to / reference / explanation). Use when adding, restructuring, or reviewing a docs/*.md file — keeps each doc to one quadrant. Excludes design, spec, plan, and archive documents.

Riverpod 3 Notifier patterns, go_router routing, SharedPreferences persistence, and Flutter UI conventions for fs-game-score. Use for any feature work or provider change, splash/score-table flows, adding or translating user-facing strings (.arb files, gen-l10n), localizing semantic labels, and Mille Bornes / game-mode terminology — even when the request doesn't mention architecture or l10n by name.

LAN host/spectator live score sync for this app: WebSocket wire protocol, mDNS discovery, QR-code join, PIN and app-version validation, and the host/join/ spectator UI. Use when changing gameSyncHostProvider, gameSyncSpectatorProvider, the join or live-share screens, the connection banner, or anything mentioning spectators, live sharing, QR scan, or ws:// URLs.

Version tagging, pubspec/CHANGELOG bumps, distributable builds, and store release notes for fs-game-score. Use when cutting a release, running tag-push.sh, or preparing CHANGELOG sections.

Procedure for upgrading the Flutter and Dart SDK versions across the monorepo. Covers FVM config, GitHub actions, pubspec.yaml constraints, and changelogs.

Unit, widget, and integration testing patterns for this app: ProviderScope overrides, integration_test helpers (launchApp, waitForScoreTable, pumpUntilFound), fake sync transports, widget-key lookups in tests, and accessibility/semantics checks. Use whenever writing, fixing, or reviewing any test, debugging a flaky integration flow or splash-clear race, or changing screen-reader/a11y behavior.

Widget keys, semantics, and modal layout rules for player/round UI in this app. Use when editing score table cells, modals, splash configuration, or form fields.

Build, run, drive, and screenshot the fs_score_card Flutter app. Use when asked to start the app, launch it, run its integration flow, take a screenshot of its UI, or confirm a change works in the real running app (not just tests).