القائمة
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.
التثبيت باستخدام 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.
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/`.
| name | adaptive-cards-code-review |
| description | 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. |
Use this skill as a "Final Gate" for any PR or significant change. Cross-reference with specialized skills (adaptive-cards-spec-compliance, adaptive-cards-element-registry, adaptive-cards-public-api-docs, adaptive-cards-testing) as needed.
flutter, dart) executed via fvm?fvm flutter analyze? (Compliance with very_good_analysis).CHANGELOG.md been updated in the affected packages following Keep a Changelog?adaptive-cards-release-engineer — all six version: fields match, six changelogs have matching top ## [<version>] sections, and flutter_adaptive_charts_fs and flutter_adaptive_cards_host_fs use flutter_adaptive_cards_fs: ^<version>.dart_format been run on all modified files?/// docs: Do exported API changes in library packages explain why and how to use the API (not implementation steps)? See adaptive-cards-public-api-docs.docs/)Architecture docs drift silently. If this change touches any of the triggers below, git grep the affected symbols in docs/ and confirm the canonical docs were updated in this change (see the "Architecture documentation sync gate" in AGENTS.md).
ProviderScope (including nested scopes), or move a provider between scopes? → Update docs/reactive-riverpod.md (provider scopes + diagram) and docs/Architecture-Overview.md (scope diagram).AdaptiveVisibilityMixin.isVisible, AdaptiveInputMixin)? → Update the relevant section of docs/reactive-riverpod.md.docs/hostconfig.md, the owning package's README ## Implementation status table (packages/flutter_adaptive_cards_fs/README.md for core; charts/templating in their package READMEs), and docs/overlay-properties-by-type.md as applicable. docs/Implementation-Status.md is an index — edit it only for the project-level roadmap/history or pointers, not per-component status or known gaps (those live in the package READMEs).git grep -n '<removed-or-renamed-symbol>' docs/ returns nothing pointing at deleted/renamed code (a stale doc reference is a blocker, not a nit).docs/*.md or a package README), does the doc stay within one Diátaxis quadrant, and does its doc_type: front matter (tutorial / how-to / reference / explanation) match? A newly introduced mode-mix in a previously-pure doc is drift to fix in this change, not a nit. Out-of-scope artifacts (plans/, reviews/, archive/, dated specs) are exempt. See the adaptive-cards-diataxis-docs skill.flutter_adaptive_cards_fs ChecklistCardTypeRegistry or ActionTypeRegistry?AdaptiveElementWidgetMixin (Widget) and AdaptiveElementMixin + AdaptiveVisibilityMixin (State)?AdaptiveInputMixin? On user change, does it call setDocumentInputValue(...)? Does it sync controllers in onDocumentValueChanged when overlays change (reset)?AdaptiveVisibilityMixin and write via setIsVisible / document notifier (not local-only setState)?AdaptiveTextBlock read display copy from resolvedElementProvider(id) (not only stale adaptiveMap['text'])?isEnabled via AdaptiveActionStateMixin / resolvedActionProvider when host-driven enable/disable matters?setInputValue, setText, setInputError, …) rather than mutating the host JSON map?flutter_adaptive_cards_fs avoid chart-specific (or other optional-package) types, imports, and overlay fields? Optional behavior belongs in extension packages via addedElements / overlayExtensions, not in core.styleResolver (via ProviderScopeMixin) or ProviderScope.containerOf(context).read(styleReferenceResolverProvider) for all colors, font sizes, and spacing?cardTypeRegistry / actionTypeRegistry from ProviderScopeMixin (not from ReferenceResolver)?SeparatorElement?generateAdaptiveWidgetKey(adaptiveMap)?id (e.g., ValueKey(id) or ValueKey('${id}_suffix'))? Crucial for testing stability.Full contract and testing patterns: adaptive-cards-accessibility.
altText used as the accessible name — and is an absent altText passed through as null (decorative) rather than a placeholder string?labelInputSemantics() and the visible label wrapped in ExcludeSemantics? (Both, or the name is announced twice.)Semantics(liveRegion: true)?header: true + headingLevel, and do interactive targets expose both a name and a role?tester.ensureSemantics()?semanticsLabel: (see adaptive-cards-localization).lib/flutter_adaptive_cards_fs.dart?lib/flutter_adaptive_cards_extend.dart if intended for customization by consumers?/// docs: Do new or changed exported members explain why the API exists and how callers use it — not implementation steps? See adaptive-cards-public-api-docs.flutter_adaptive_template_fs Checklist$data, $root, $index, and $when handled correctly during expansion?$data correctly shift the resolution context?flutter_adaptive_cards_host_fs ChecklistAdaptiveCardBackendHandlers shares the same GlobalKey<RawAdaptiveCardState> as RawAdaptiveCard when onSubmit / onExecute / onRefresh need card state.AdaptiveCardInvokeResponse.applyTo.pubspec.yaml declares flutter_adaptive_cards_fs: ^<monorepo-version> (sync on release bump).packages/flutter_adaptive_cards_host_fs/test/ (no goldens); run fvm flutter test from that package directory.docs/backend-host-integration.md and package README.md; exported /// comments follow adaptive-cards-public-api-docs.See adaptive-cards-backend-host skill for file paths and invoke round-trip patterns.
find.text() or find.byType() calls in tests should be replaced with find.byKey() whenever a key is available.test/samples/ demonstrating the feature/fix?--update-goldens on macOS, then copy each new PNG from test/gold_files/macos/ to test/gold_files/linux/ so CI has a baseline (see adaptive-cards-testing skill and test/gold_files/README.md).linux/ files from CI artifact zips for canonical Linux images.tool/coverage_floors.yaml. The CI coverage gate (golden-excluded line coverage) must stay green — add tests rather than lowering a floor. Raising a floor after landing tests is fine; lowering one to pass is a red flag. See docs/testing-coverage.md.widgetbook changes (sample app)widgetbook/lib/samples/ are listed in widgetbook/pubspec.yaml under flutter: assets: (required for AdaptiveCardsCanvas.asset).@widgetbook.UseCase added or updated in adaptive_cards_use_cases.dart; fvm dart run build_runner build run when use cases change.widgetbook/CHANGELOG.md updated when the demo app changes.docs/widgetbook-overlay-demos.md; package behavior docs tag widgetbook as Example (widgetbook sample) per documentation-scope.md.When performing a review, summarize findings using this format:
### Code Review Summary
- **Package**: [e.g. flutter_adaptive_cards_fs]
- **Hygiene**: [PASS/FAIL] (Analysis, Changelog, Formatting)
- **Docs impact**: [PASS/FAIL/N-A] (canonical `docs/` synced; no stale references)
- **Compliance**: [PASS/FAIL] (Registry, Spec, Theming)
- **Testing**: [PASS/FAIL] (Keys, Samples, Goldens)
#### Details
- [Specific feedback regarding keys, accessibility, etc.]