freemansoft

Semantics contract for Adaptive Card elements — how labels, headings, live regions, and decorative-vs-meaningful images are exposed to screen readers, and how to test them with `tester.ensureSemantics()`. Use when adding or changing any element, input, or action widget, and at code review.

Optional flutter_adaptive_cards_host_fs package — backend invoke serialization, PlainJson/Teams adapters, AdaptiveCardBackendHandlers, and response effects. Use when wiring Submit/Execute/Refresh/onChange to a flow-service or reviewing associatedInputs + invoke round-trips.

Use when finalizing a change in the Flutter-AdaptiveCards monorepo — before you propose, commit, or merge — as the manual or AI-assisted review gate. Checks monorepo hygiene, Adaptive Cards spec compliance, theming, widget keys, accessibility, and testing.

FVM rules for the Flutter-AdaptiveCards monorepo. Prefix every `flutter` and `dart` shell command with `fvm`. Use when vendored dart/flutter skills show bare commands, when installing or switching the pinned SDK, or before analyze, test, pub, or build_runner workflows.

Classify, audit, and enforce the Diátaxis documentation framework across the Flutter-AdaptiveCards canonical `docs/` and package READMEs. Keeps each doc in exactly one quadrant (tutorial / how-to / reference / explanation) and flags mixed-mode drift. Use when writing or reviewing a doc under `docs/`, adding a `doc_type:` front-matter tag, auditing the doc set for gaps or violations, or when the user mentions Diátaxis or documentation structure. Advisory only — it proposes splits, it does not silently move or rewrite files.

Use before adding a new Adaptive Card element type — implementing its widget, registering it, or testing it. Covers the StatefulWidget + mixin pattern, CardTypeRegistry registration, the extension API, and optional packages (charts).

Use when writing or reviewing model (de)serialization or theming in this repo, or before adding a `fromJson`/`toJson`. The library packages diverge from two things generic Flutter skills assume: they hand-write serialization (no `json_serializable` / code-gen) and style elements from HostConfig (not app-level `ThemeData`/`GoogleFonts`). Read this when a generic skill or habit points you at `@JsonSerializable`, `build_runner` for models, or `ColorScheme` app theming inside `packages/`.

Use before modifying styling, colors, spacing, fonts, or HostConfig parsing in any element. Explains how Adaptive Cards HostConfig maps to Flutter rendering, how ReferenceResolver bridges the two, and how light/dark themes are structured.

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).

Use this skill for any work on this docker-scripts repo's container examples — adding a brand-new service example (new subdirectory with docker-compose.yml + README.md, plus a row in the root README table), tuning an existing example's resource limits/ports/env vars/OS-level settings, or upgrading an example to a newer version of the underlying software with today's upstream baseline. Trigger on requests like "add a new container/example for X", "scaffold a docker-compose for Y", "set up Z in this repo", "tune/adjust the memory/ports/env vars for the <service> example", "why is <service> running out of memory", "upgrade <service> to the latest version", "bump the <service> image version", or "is <service>'s example out of date" — even if the user doesn't say "skill" or name this repo's conventions explicitly.