umacapture

Bring a fresh umacapture clone to a buildable state end to end: check for the required external toolchain (FVM-pinned Flutter 3.44.4, uv, Visual Studio 2022 C++, optional 7-Zip) -- never installing host-level tools unprompted, only with the user's approval -- provision the gitignored Windows native dependencies via tool/fetch_deps.py, enable the git hooks and blame-ignore config, resolve Dart packages, and run build_runner codegen. Use when someone is setting up the project for the first time, asks "how do I get this building", hits a missing-SDK / missing-OpenCV / unformatted-hook / codegen error on a new machine, or wants the canonical first-time setup sequence. Points at the native-cli-dev and release skills for the deeper native-build and publishing flows.

Cut a new umacapture release end to end: bump the app version in pubspec.yaml, regenerate the version/license assets via build_runner, land the bump on the protected develop branch via a release/v<version> PR, tag the merge commit, then build and publish the Windows exe + zip to a GitHub release with flutter_distributor. Covers the two phases (version bump + codegen + PR merge, then tag + flutter_distributor deploy), the FVM/Inno Setup/GITHUB_TOKEN prerequisites, and the known-broken global flutter_distributor activation under Dart 3.12. Use when the user wants to release, ship, publish, or bump the app version and push a new build to GitHub releases.

Fetch and inspect this app's Sentry error reports from the command line via the Sentry REST API. Use whenever the user wants to check, look at, triage, or pull umacapture's Sentry issues, crash reports, or error logs — e.g. "check Sentry", "what errors are users hitting", "show the latest crashes", "is there anything new on release X", or when they want the full stack trace / tags / context of a specific issue. Covers the production project (the debug project no longer receives events), the release-version filter, and the difference between readable Dart exceptions and unsymbolicated native crashes.

Build, run, log, and debug the C++ capture/recognition backend in native/ as a standalone CLI (umacapture_cli) from the command line, without CLion. Sets up the MSVC toolchain via vcvars64, configures CMake with Ninja (Debug/Release), runs the build / capture / screenshot / video / replay / stitch / recognize subcommands, explains the spdlog output and which subcommands self-terminate vs. run a live event loop, and steps through the binary with the cdb command-line debugger. Use when the user wants to build, rebuild, run, inspect logs from, or debug the native CLI, regenerate the assets/config/*.json scene definitions, record or replay FFV1 capture recordings, or test capture/recognition logic outside the Flutter app.

Use after ANY UI under lib/ is added or changed — new widgets, screens, or dialogs; restyled or recolored components; added, removed, or recolored colors; new ColorScheme roles, ThemeExtension tokens, or translucent/alpha composites. Treat this as mandatory whenever a change touches the UI, so the in-app debug theme gallery never drifts from the code. Also use when the user asks to update, regenerate, or re-sync the theme/color gallery, or when its swatches, usage descriptions, "used vs unused" marks, or translucent-composite list look stale.

Install or update Flutter's official AI rules into this repo, pruned to remove anything that conflicts with this project's conventions. Vendors the upstream rules file from flutter/flutter into .claude/rules/flutter-ai-rules.md (auto-loaded by Claude Code), re-surveys it against the current project state for conflicts, then deletes/rewrites the conflicting passages so only project-safe guidance remains. Use when the user wants to install, refresh, re-sync, or switch the size variant of the official Flutter/Dart AI rules.