OpenParable
Skip to content
← Back to skills

Build And Run Macos App

Development
build-and-run-macos-app

Build And Run Macos App is an Agent Skill for development published in the robinebers/openusage repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Slash command that creates or updates the project-local macOS `script/build_and_run.sh` and uses it as the default build/run entrypoint. Invoke explicitly with /build-and-run-macos-app — this skill never self-triggers.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/robinebers/openusage/blob/HEAD/.agents/skills/build-and-run-macos-app/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/build-and-run-macos-app, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Build And Run macOS App

Create or update the project-local macOS build_and_run.sh script, then use that script as the default build/run entrypoint.

Arguments

  • scheme: Xcode scheme name (optional)
  • workspace: path to .xcworkspace (optional)
  • project: path to .xcodeproj (optional)
  • product: SwiftPM executable product name (optional)
  • mode: run, debug, logs, telemetry, or verify (optional, default: run)
  • app_name: process/app name to stop before relaunching (optional)

Workflow

  1. Detect whether the repo uses an Xcode workspace, Xcode project, or SwiftPM package.
  2. If the workspace is not inside git yet, run git init at the project root so git-backed editor features unlock.
  3. Create or update script/build_and_run.sh so it always stops the current app, builds the macOS target, and launches the fresh result.
  4. For SwiftPM, keep raw executable launch only for true CLI tools; for AppKit/SwiftUI GUI apps, create a project-local .app bundle and launch it with /usr/bin/open -n.
  5. Support optional script flags for --debug, --logs, --telemetry, and --verify.
  6. Follow the canonical bootstrap contract in ../build-run-debug/references/build-script.md for the exact script shape.
  7. Run the script in the requested mode and summarize any build, script, or launch failure.

Guardrails

  • Do not initialize a nested git repo inside an existing parent checkout.
  • Keep the no-flag script path simple: kill, build, run.
  • Use --debug, --logs, --telemetry, or --verify only when the user asks for those modes.