메뉴
Build, run, drive, and screenshot the adaptive_explorer macOS desktop app. Use when asked to start/launch/run adaptive_explorer, take a screenshot of it, confirm a change renders in the real app, or run its tests.
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 | run-adaptive-explorer |
| description | Build, run, drive, and screenshot the adaptive_explorer macOS desktop app. Use when asked to start/launch/run adaptive_explorer, take a screenshot of it, confirm a change renders in the real app, or run its tests. |
adaptive_explorer is a Flutter desktop app (macOS/Linux/Windows — no web,
no mobile: it uses dart:io file-watching and native file dialogs). The agent
path builds and launches the real macOS app and captures a PNG from inside the
process, driven by
.claude/skills/run-adaptive-explorer/drive.sh →
driver_main.dart.
All paths below are relative to adaptive_explorer/. Every flutter/dart
command is prefixed with fvm (the repo pins its SDK — Flutter 3.44.0 — via
FVM; bare flutter may be the wrong version).
xcodebuild.fvm install (reads ../.fvmrc).fvm flutter devices (look for
macOS (desktop)).There is no Linux container path here: this is a native desktop GUI and the driver was verified on macOS only.
From the repo root (this is a pub workspace — one resolve covers every package):
cd ..
fvm flutter pub get
cd adaptive_explorer
.claude/skills/run-adaptive-explorer/drive.sh
What it does, with no human input:
fvm flutter run -d macos -t .claude/skills/run-adaptive-explorer/driver_main.dart
— launches the real app. driver_main.dart boots it with a card already
loaded (via the app's initialTemplateJson test seam) so there is content
to see without clicking a native file dialog.RepaintBoundary → PNG) into
its sandbox temp dir and prints SCREENSHOT_WRITTEN: <path>../adaptive_explorer_screenshot.png and quits
the app.Pass a custom output path as the first argument:
.claude/skills/run-adaptive-explorer/drive.sh /tmp/ae.png
First macOS build takes ~2–4 min; incremental runs are ~30–60s. The trailing
Terminated: 15 line is the script quitting the app — it is expected, exit code
is still 0.
Verified result — the PNG shows the "Adaptive Explorer" app bar (Open Template / Open Data / Save), the preview pane, the Template/Data/Merged tabs, and the injected card JSON in the editor.
Opens a real window and blocks until you press q:
fvm flutter run -d macos # empty "Select a template to view" screen
Then use the Open Template / Open Data buttons to load JSON from disk; the preview pane re-renders on file save (file-watching). Useless headless — it just waits for a window nobody can see.
fvm flutter test
Verified: 24 tests pass (template_manager_test.dart, widget_test.dart).
macos/Runner/DebugProfile.entitlements).
The app cannot write a PNG to the repo dir or /tmp — writeAsBytes there
fails with Operation not permitted. driver_main.dart writes to
Directory.systemTemp (inside its container, still readable by the
unsandboxed shell) and prints the path; drive.sh copies it out.screencapture does not work from a sandboxed/headless shell — it needs
Screen Recording permission and returns could not create image from display.
That is why capture happens inside the app, not via the OS.flutter screenshot is useless here — it only produces PNGs for physical
Android/iOS devices; for desktop it errors VM Service URI cannot be provided for screenshot type device.fvm flutter run -d chrome will not compile — the app
imports dart:io (file watcher). Desktop only.initialTemplateJson seam sets the editor tabs but the merge pipeline that
feeds the preview only runs when a file is loaded from disk, so the screenshot
shows No preview available in the preview pane. That is a limitation of the
seam, not a bug in your change.Target file ".claude/…/driver_main.dart" not found → you are not in
adaptive_explorer/. cd there first (the target path is relative).flutter run exited early in the drive log → run
fvm flutter run -d macos -t .claude/skills/run-adaptive-explorer/driver_main.dart
directly to see the real compile error.