Agent skill
flutter-setting-up-on-macos
Sets up a macOS environment for Flutter development. Use when configuring a macOS machine to run, build, or deploy Flutter applications for iOS or macOS.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/flutter-setting-up-on-macos
Metadata
Additional technical details for this skill
- model
- models/gemini-3.1-pro-preview
- last modified
- Thu, 12 Mar 2026 22:12:50 GMT
SKILL.md
Setting Up a macOS Environment for Flutter Development
Contents
- Prerequisites
- Tooling Configuration
- Workflow: Configuring macOS Tooling
- Workflow: Validating the Environment
- Troubleshooting
Prerequisites
Ensure the following baseline requirements are met before configuring the macOS-specific toolchain:
- macOS operating system.
- Flutter SDK installed and added to the system
PATH. - Active internet connection for downloading toolchains and dependencies.
Tooling Configuration
macOS desktop development requires specific Apple toolchains to compile and debug native Swift and Objective-C code.
- Xcode: Required for compiling macOS desktop applications.
- CocoaPods: Required for managing native dependencies used by Flutter plugins.
Workflow: Configuring macOS Tooling
Copy and follow this checklist to configure the macOS build environment.
- Install Xcode: Install the latest version of Xcode from the Mac App Store or the Apple Developer portal.
- Configure Command-Line Tools: Link the Xcode command-line tools to the installed Xcode version. Run the following command in the terminal:
bashConditional: If Xcode is installed in a custom directory, replace
sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch'/Applications/Xcode.appwith the correct absolute path. - Accept Xcode Licenses: Accept the required developer licenses by running:
bashRead and agree to the prompts.
sudo xcodebuild -license - Install CocoaPods: Install CocoaPods to handle native macOS plugin dependencies.
bashConditional: If CocoaPods is already installed, ensure it is updated to the latest version (
sudo gem install cocoapodssudo gem update cocoapods).
Workflow: Validating the Environment
Execute this feedback loop to ensure the environment is correctly configured for macOS desktop development.
- Run Validator: Execute the Flutter diagnostic tool with verbose output:
bash
flutter doctor -v - Review Errors: Check the
Xcodesection in the output. - Fix & Retry: If errors or missing components are reported under the Xcode section, resolve them according to the output instructions, then re-run
flutter doctor -vuntil the Xcode section passes. - Verify Device Availability: Confirm that Flutter recognizes the macOS desktop as a valid deployment target:
bashSuccess Criteria: The output must contain at least one entry with
flutter devicesmacoslisted as the platform.
Troubleshooting
If the validation workflow fails, apply the following resolutions:
- Missing Command-Line Tools: If
flutter doctorreports missing tools, ensure thexcode-selectcommand was run withsudoand points to the correct.appdirectory. - CocoaPods Not Found: If CocoaPods is installed but not detected, verify that your Ruby
gembinary path is included in your shell'sPATHenvironment variable. - Device Not Listed: If
flutter devicesdoes not listmacos, ensure desktop support is enabled in your Flutter configuration:bashflutter config --enable-macos-desktop
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?