Update to Build macOS Apps

{
  "name": "swiftpm-macos",
  "description": "Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 268
    }
  ],
  "skill_md_contents": "---\nname: swiftpm-macos\ndescription: Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.\n---\n\n# SwiftPM for macOS\n\n## Quick Start\n\nUse this skill when `Package.swift` is the primary entrypoint or when SwiftPM is\nthe fastest path to a reproducible result.\n\n## Workflow\n\n1. Inspect the package.\n   - Read `Package.swift`.\n   - Identify executable, library, and test products.\n\n2. Build with SwiftPM.\n   - Use `swift build` by default.\n   - Use release mode only when the user explicitly needs it.\n\n3. Run the right product.\n   - Use `swift run <product>` when an executable exists.\n   - If multiple executables exist, explain the default choice.\n\n4. Test narrowly.\n   - Use `swift test`.\n   - Apply filters when a specific test target or case is known.\n\n5. Summarize failures.\n   - Module/import resolution\n   - Package graph or dependency issue\n   - Linker failure\n   - Runtime failure\n   - Test regression\n\n## Guardrails\n\n- Prefer SwiftPM over Xcode when both exist and the package path is clearly simpler.\n- Do not assume an app bundle exists in a pure package workflow.\n- Explain when the package is library-only and therefore not directly runnable.\n\n## Output Expectations\n\nProvide:\n- the package products you found\n- the command you ran\n- whether build, run, or test succeeded\n- the top blocker if not\n"
}