windows-flutter-exe
Build, verify, and package Flutter desktop apps for Windows into a distributable executable bundle (EXE plus required DLL/data dependencies, optional installer-ready artifacts). Use when a user asks to generate a Windows Flutter executable, ship a Windows desktop release, include runtime dependencies, or troubleshoot missing DLL/runtime issues in Windows Flutter distribution.
Best use case
windows-flutter-exe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build, verify, and package Flutter desktop apps for Windows into a distributable executable bundle (EXE plus required DLL/data dependencies, optional installer-ready artifacts). Use when a user asks to generate a Windows Flutter executable, ship a Windows desktop release, include runtime dependencies, or troubleshoot missing DLL/runtime issues in Windows Flutter distribution.
Teams using windows-flutter-exe should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/windows-flutter-exe/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How windows-flutter-exe Compares
| Feature / Agent | windows-flutter-exe | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build, verify, and package Flutter desktop apps for Windows into a distributable executable bundle (EXE plus required DLL/data dependencies, optional installer-ready artifacts). Use when a user asks to generate a Windows Flutter executable, ship a Windows desktop release, include runtime dependencies, or troubleshoot missing DLL/runtime issues in Windows Flutter distribution.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Windows Flutter Executable Packaging ## Overview Produce a Windows Flutter release bundle that runs on end-user machines by packaging the complete `build/windows/x64/runner/Release` output instead of only the `.exe`. Use this workflow to avoid broken deliveries caused by missing plugin DLLs, `flutter_windows.dll`, or `data/` assets. ## Required Inputs - App root containing `pubspec.yaml` - Windows build host (or CI runner) with Flutter + Visual Studio C++ desktop workload - Target architecture (default: `x64`) - Output directory for shipping artifacts ## Workflow ### 1) Preflight - Confirm Windows target is enabled: ```bash flutter config --enable-windows-desktop ``` - Confirm toolchain: ```bash flutter doctor -v ``` - Ensure `flutter doctor` shows no blocking Windows desktop issues. ### 2) Build Release - From app root: ```bash flutter pub get flutter build windows --release ``` - Release output location: `build/windows/x64/runner/Release` ### 3) Bundle All Runtime Dependencies Package the full `Release` folder, not only `<app>.exe`. Required runtime surfaces: - `<app>.exe` - `flutter_windows.dll` - `data/` directory - Plugin/native DLLs generated by Flutter plugins ### 4) Create a Distributable Archive Run the bundled helper: ```bash bash ./skills/windows-flutter-exe/scripts/build_windows_flutter_bundle.sh \ --app-root <APP_ROOT> \ --out-dir <OUTPUT_DIR> ``` This script can: - Build Windows release - Validate required runtime files - Copy full Release payload into a versioned bundle directory - Generate SHA256 manifest - Produce a `.zip` artifact ### 5) Optional VC++ Redistributable Inclusion If your distribution policy requires bundling the VC++ runtime installer, provide it to the script: ```bash bash ./skills/windows-flutter-exe/scripts/build_windows_flutter_bundle.sh \ --app-root <APP_ROOT> \ --out-dir <OUTPUT_DIR> \ --vc-redist-path <PATH_TO_VC_REDIST_X64_EXE> ``` ### 6) Clean-Machine Validation (Release Gate) - Test the packaged bundle on a clean Windows machine/VM. - Confirm app launch without missing DLL errors. - Confirm plugin features that depend on native libraries. ## Troubleshooting - `Missing flutter_windows.dll`: package entire `Release` directory, not exe-only. - `MSVCP140.dll` or `VCRUNTIME140.dll` errors: install or ship Microsoft Visual C++ Redistributable (x64). - App runs locally but not on user machine: validate on clean VM and compare bundle contents with CI artifact. - Plugin feature fails in release only: verify plugin DLLs are present in packaged bundle. ## Deliverables Checklist - [ ] `windows-x64/` folder containing exe + all dependencies - [ ] `windows-x64.zip` archive - [ ] `SHA256SUMS.txt` - [ ] Optional `vc_redist.x64.exe` inside bundle (if policy requires)
Related Skills
osx-flutter-auth0-login
Use when adding login/authentication to a Flutter macOS app (desktop) using Auth0. Includes Auth0 tenant setup, macOS callback configuration, Flutter login UI and AuthService, secure token storage, logout, and a backend JWT verification example.
osx-review
Use when preparing mobile/desktop apps for App Store submission, before final release, or when user mentions App Store, production readiness, shipping, or needs comprehensive quality review for distribution
osx-ios
Use when preparing iOS and iPadOS apps for TestFlight or App Store release, including signing, archive/IPA export, App Store Connect metadata, privacy/compliance checks, and final distribution readiness.
osx-compliance
Use when auditing Apple-platform app projects for release infrastructure and distribution compliance. Covers macOS DMG readiness and iOS/iPad App Store Connect release gates via companion checks.
osx-blockers
Use when conducting deep code review for production blockers including API mismatches, memory leaks, busy wait loops, and UI workflow failures. Apply before release to catch runtime bugs that static analysis misses.
github-issue-fix
Reproduce, diagnose, fix, verify, commit, and push changes for GitHub issue reports and bug tickets. Use when the user provides a GitHub issue URL/number, asks to reproduce a reported crash or workflow failure, wants a blocker-first debugging workflow, or needs issue-linked commit/push notes after a verified fix.
performing-windows-artifact-analysis-with-eric-zimmerman-tools
Perform comprehensive Windows forensic artifact analysis using Eric Zimmerman's open-source EZ Tools suite including KAPE, MFTECmd, PECmd, LECmd, JLECmd, and Timeline Explorer for parsing registry hives, prefetch files, event logs, and file system metadata.
hunting-for-persistence-mechanisms-in-windows
Systematically hunt for adversary persistence mechanisms across Windows endpoints including registry, services, startup folders, and WMI subscriptions.
hardening-windows-endpoint-with-cis-benchmark
Hardens Windows endpoints using CIS (Center for Internet Security) Benchmark recommendations to reduce attack surface, enforce security baselines, and meet compliance requirements. Use when deploying new Windows workstations or servers, remediating audit findings, or establishing organization-wide security baselines. Activates for requests involving Windows hardening, CIS benchmarks, GPO security baselines, or endpoint configuration compliance.
extracting-windows-event-logs-artifacts
Extract, parse, and analyze Windows Event Logs (EVTX) using Chainsaw, Hayabusa, and EvtxECmd to detect lateral movement, persistence, and privilege escalation.
configuring-windows-event-logging-for-detection
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving Windows audit policy, event log configuration, security logging, or detection-oriented logging.
configuring-windows-defender-advanced-settings
Configures Microsoft Defender for Endpoint (MDE) advanced protection settings including attack surface reduction rules, controlled folder access, network protection, and exploit protection. Use when hardening Windows endpoints beyond default Defender settings, deploying enterprise-grade endpoint protection, or meeting compliance requirements for advanced malware defense. Activates for requests involving Windows Defender configuration, ASR rules, MDE tuning, or Microsoft endpoint security.