メニュー
Use when upgrading the pinned Flutter/Dart SDK version across the monorepo — updating FVM config, GitHub Actions, pubspec.yaml SDK constraints, and changelogs so every package and CI pipeline stays in sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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).
| name | adaptive-cards-release-flutter-upgrade-sdk |
| description | Use when upgrading the pinned Flutter/Dart SDK version across the monorepo — updating FVM config, GitHub Actions, pubspec.yaml SDK constraints, and changelogs so every package and CI pipeline stays in sync. |
Follow this procedure when upgrading the Flutter and Dart SDK versions used in this monorepo. Ensuring all configurations, packages, and CI pipelines stay in sync is critical for monorepo health.
FVM is the source of truth for the local development environment. fvm flutter --version will automatically update the fvm managed local flutter to the correct version if it is not already installed.
You can manually update flutter versions by running:
fvm install <new-flutter-version> (e.g., fvm install 3.41.2) in the root of the repository if the new target version of flutter is not already installed.fvm use <new-flutter-version> (e.g., fvm use 3.41.2) in the root of the repository..fvm/fvm_config.json has been updated with the new version.The GitHub Actions workflows must use the exact same Flutter version as FVM to prevent CI drifts.
.github/workflows/test.yml.subosito/flutter-action step.flutter-version: parameter to match the new FVM version exactly.pubspec.yaml FilesAll packages in the monorepo should share the same minimum Dart/Flutter SDK requirements.
Locate all pubspec.yaml files across the repository. This includes:
packages/flutter_adaptive_cards_fs/pubspec.yaml
packages/flutter_adaptive_charts_fs/pubspec.yaml
packages/flutter_adaptive_template_fs/pubspec.yaml
packages/flutter_adaptive_cards_host_fs/pubspec.yaml
adaptive_explorer/pubspec.yaml
widgetbook/pubspec.yaml
Update the environment: constraints to match the new minimum Dart SDK (and optionally Flutter SDK) corresponding to the new Flutter version.
environment:
sdk: ^<new-dart-version>
Document the SDK bump so consumers of the packages are aware of the new minimum requirements.
CHANGELOG.md file for every updated package under the Unreleased or upcoming version heading.- Require Dart SDK <new-dart-version> and Flutter <new-flutter-version>Ensure that the new SDK version does not break existing code or cause new linting errors.
fvm flutter pub get or upgrade at the workspace root).fvm flutter analyze to catch any new static analysis errors or deprecations introduced by the newer SDK.fvm flutter test to ensure all tests continue to pass.