ClaudeCodeMod

All shelves / Skills

flutter-setting-up-on-macos

flutter/agent-plugins · 7.8k installs · 3.1K stars

Skill

Marked Command Execution · External Downloads

Install

In your shell
npx -y skills add flutter/agent-plugins --skill flutter-setting-up-on-macos --agent claude-code

Run in a terminal. Claude loads the skill when a task calls for it. Check the repo's README before you run it.

Open the repo

Files

SKILL.md

Setting Up a macOS Environment for Flutter Development

Contents

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:
    sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch'
    
    Conditional: If Xcode is installed in a custom directory, replace /Applications/Xcode.app with the correct absolute path.
  • Accept Xcode Licenses: Accept the required developer licenses by running:
    sudo xcodebuild -license
    
    Read and agree to the prompts.
  • Install CocoaPods: Install CocoaPods to handle native macOS plugin dependencies.
    sudo gem install cocoapods
    
    Conditional: If CocoaPods is already installed, ensure it is updated to the latest version (sudo 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:
    flutter doctor -v
    
  • Review Errors: Check the Xcode section 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 -v until the Xcode section passes.
  • Verify Device Availability: Confirm that Flutter recognizes the macOS desktop as a valid deployment target:
    flutter devices
    
    Success Criteria: The output must contain at least one entry with macos listed as the platform.

Troubleshooting

If the validation workflow fails, apply the following resolutions:

  • Missing Command-Line Tools: If flutter doctor reports missing tools, ensure the xcode-select command was run with sudo and points to the correct .app directory.
  • CocoaPods Not Found: If CocoaPods is installed but not detected, verify that your Ruby gem binary path is included in your shell's PATH environment variable.
  • Device Not Listed: If flutter devices does not list macos, ensure desktop support is enabled in your Flutter configuration:
    flutter config --enable-macos-desktop
    

Facts

Kind
Skill
Repo
flutter/agent-plugins
Group
Uncategorized
Installs
7.8k
Stars
3.1K

More on this shelf

  1. 1find-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.3.8M
  2. 2grill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.3M
  3. 3grill-with-docsmattpocock/skillsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.1.1M
  4. 4agent-browservercel-labs/agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.1.1M
  5. 5improve-codebase-architecturemattpocock/skillsScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.1.1M
  6. 6tddmattpocock/skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.1.1M