macos-spm-app-packaging

What This Skill Does

The macos-spm-app-packaging skill provides an automated, Xcode-independent workflow for creating, building, and deploying macOS applications. By utilizing the Swift Package Manager (SwiftPM) as the primary project structure, this skill removes the overhead and complexity associated with monolithic .xcodeproj files. It includes a library of battle-tested shell scripts for common build tasks, ranging from local development cycles to full code-signing, notarization, and Sparkle appcast generation. This allows developers to manage the entire lifecycle of a native macOS app—including icon generation, bundle creation, and binary distribution—directly through command-line automation and the OpenClaw agent.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/dimillian/macos-spm-app-packaging

Ensure that you have the Swift toolchain and standard macOS Command Line Tools installed, as the build scripts depend on the swift compiler and system-level security binaries like codesign and altool for notarization.

Use Cases

• Lightweight App Development: Ideal for developers who prefer text-editor-based workflows (like VS Code or Neovim) instead of the full Xcode IDE.
• CI/CD Pipeline Integration: Automate the entire release process, including code-signing and notarization, without needing a GUI-based build server.
• Open Source Projects: Simplify contribution by making the build process transparent, scriptable, and platform-agnostic, removing the "it works on my machine" issues associated with Xcode project settings.
• Menubar App Creation: Rapidly bootstrap and deploy lightweight background applications with specialized build settings for LSUIElement configurations.

Example Prompts

1. "Bootstrap a new macOS SwiftPM project named 'NetworkMonitor' in the current directory, renaming all placeholders to match this name."
2. "Update my project's build version in version.env and run the package_app.sh script to prepare a fresh notarized release for GitHub."
3. "Help me integrate the Sparkle framework by generating an updated appcast entry after I build the latest binary version of my utility."

Tips & Limitations

• Version Management: Always increment the BUILD_NUMBER in your version.env file before initiating a release build, as Sparkle and macOS gatekeeper validation rely on these version identifiers.
• Icon Assets: Generating an .icns file requires an Xcode installation to use the Icon Composer utility, though the build script automates the final packaging phase.
• Explicit Configuration: Because this workflow avoids the Xcode GUI, project settings (like Entitlements and Info.plist) must be maintained manually in the script files. Check the assets/templates/ folder frequently to ensure your local scripts are synced with the latest best practices provided by the package.