Skip to main content
skill CX Codex

build-macos-apps — Claude Code skill for native macOS apps

build-macos-apps is a Claude Code skill for building native macOS apps with SwiftUI and AppKit. It routes work on new apps, bugs, tests, performance, and releases to a matching workflow.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What build-macos-apps does

The skill guides macOS app work through focused workflows for creating an app, debugging it, adding a feature, writing tests, tuning performance, or preparing a release. Each task maps to a file in workflows/; the references/ directory covers topics such as app architecture, persistence, system APIs, and testing.

After a change, the workflow checks the build and tests with xcodebuild. UI changes also call for launching the app for a visual check. The listed verification commands use xcsift as well. The skill is CLI-only and says it works without Xcode, while its build and test commands use xcodebuild.

What it helps with

  • build a native macOS app in Swift
  • debug a crashing macOS app
  • add a feature to an existing app
  • write and run tests
  • prepare an app for release

Example prompts for the agent

  • Build a new macOS app with SwiftUI.
  • Find and fix the bug causing my app to crash.
  • Prepare this app for release and verify the build.

How to install build-macos-apps

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

This installs the whole taches-cc-resources plugin with all its skills

2Skills CLI (Vercel)

npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a claude-code

3Manually: put the files in place

~/.claude/skills/macos-apps/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/macos-apps/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about build-macos-apps

How do I install build-macos-apps in Claude Code?

Run these commands in order: /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources.

What does build-macos-apps do?

It guides development of native macOS apps with SwiftUI and AppKit, with workflows for building, debugging, testing, performance work, and shipping.

Does build-macos-apps require Xcode?

The skill is described as CLI-only and says it works without Xcode. Its build and test steps use xcodebuild.

Source text

SKILL.md · MIT
---
name: build-macos-apps
description: Build professional native macOS apps in Swift with SwiftUI and AppKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode.
---

<essential_principles>
## How We Work

**The user is the product owner. Claude is the developer.**

The user does not write code. The user does not read code. The user describes what they want and judges whether the result is acceptable. Claude implements, verifies, and reports outcomes.

### 1. Prove, Don't Promise

Never say "this should work." Prove it:
```bash
xcodebuild build 2>&1 | xcsift  # Build passes
xcodebuild test                  # Tests pass
open .../App.app                 # App launches
```
If you didn't run it, you don't know it works.

### 2. Tests for Correctness, Eyes for Quality

| Question | How to Answer |
|----------|---------------|
| Does the logic work? | Write test, see it pass |
| Does it look right? | Launch app, user looks at it |
| Does it feel right? | User uses it |
| Does it crash? | Test + launch |
| Is it fast enough? | Profiler |

Tests verify *correctness*. The user verifies *desirability*.

### 3. Report Outcomes, Not Code

**Bad:** "I refactored DataService to use async/await with weak self capture"
**Good:** "Fixed the memory leak. `leaks` now shows 0 leaks. App tested stable for 5 minutes."

The user doesn't care what you changed. The user cares what's different.

### 4. Small Steps, Always Verified

```
Change → Verify → Report → Next change
```

Never batch up work. Never say "I made several changes." Each change is verified before the next. If something breaks, you know exactly what caused it.

### 5. Ask Before, Not After

Unclear requirement? Ask now.
Multiple valid approaches? Ask which.
Scope creep? Ask if wanted.
Big refactor needed? Ask permission.

Wrong: Build for 30 minutes, then "is this what you wanted?"
Right: "Before I start, does X mean Y or Z?"

### 6. Always Leave It Working

Every stopping point = working state. Tests pass, app launches, changes committed. The user can walk away anytime and come back to something that works.
</essential_principles>

<intake>
**Ask the user:**

What would you like to do?
1. Build a new app
2. Debug an existing app
3. Add a feature
4. Write/run tests
5. Optimize performance
6. Ship/release
7. Something else

**Then read the matching workflow from `workflows/` and follow it.**
</intake>

<routing>
| Response | Workflow |
|----------|----------|
| 1, "new", "create", "build", "start" | `workflows/build-new-app.md` |
| 2, "broken", "fix", "debug", "crash", "bug" | `workflows/debug-app.md` |
| 3, "add", "feature", "implement", "change" | `workflows/add-feature.md` |
| 4, "test", "tests", "TDD", "coverage" | `workflows/write-tests.md` |
| 5, "slow", "optimize", "performance", "fast" | `workflows/optimize-performance.md` |
| 6, "ship", "release", "notarize", "App Store" | `workflows/ship-app.md` |
| 7, other | Clarify, then select workflow or references |
</routing>

<verification_loop>
## After Every Change

```bash
# 1. Does it build?
xcodebuild -scheme AppName build 2>&1 | xcsift

# 2. Do tests pass?
xcodebuild -scheme AppName test

# 3. Does it launch? (if UI changed)
open ./build/Build/Products/Debug/AppName.app
```

Report to the user:
- "Build: ✓"
- "Tests: 12 pass, 0 fail"
- "App launches, ready for you to check [specific thing]"
</verification_loop>

<when_to_test>
## Testing Decision

**Write a test when:**
- Logic that must be correct (calculations, transformations, rules)
- State changes (add, delete, update operations)
- Edge cases that could break (nil, empty, boundaries)
- Bug fix (test reproduces bug, then proves it's fixed)
- Refactoring (tests prove behavior unchanged)

**Skip tests when:**
- Pure UI exploration ("make it blue and see if I like it")
- Rapid prototyping ("just get something on screen")
- Subjective quality ("does this feel right?")
- One-off verification (launch and check manually)

**The principle:** Tests let the user verify correctness without reading code. If the user needs to verify it works, and it's not purely visual, write a test.
</when_to_test>

<reference_index>
## Domain Knowledge

All in `references/`:

**Architecture:** app-architecture, swiftui-patterns, appkit-integration, concurrency-patterns
**Data:** data-persistence, networking
**App Types:** document-apps, shoebox-apps, menu-bar-apps
**System:** system-apis, app-extensions
**Development:** project-scaffolding, cli-workflow, cli-observability, testing-tdd, testing-debugging
**Polish:** design-system, macos-polish, security-code-signing
</reference_index>

<workflows_index>
## Workflows

All in `workflows/`:

| File | Purpose |
|------|---------|
| build-new-app.md | Create new app from scratch |
| debug-app.md | Find and fix bugs |
| add-feature.md | Add to existing app |
| write-tests.md | Write and run tests |
| optimize-performance.md | Profile and speed up |
| ship-app.md | Sign, notarize, distribute |
</workflows_index>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar skills

All skills for Programming languages →

From the same set48

The whole set →
whats-next whats-next analyzes the current conversation and writes a detailed handoff document to resume work in a fresh context. CX Codex +1 ★ 1,988repo stars the-pirate-bay Search The Pirate Bay through its JSON API and retrieve magnet links. Use it to find torrents, browse popular uploads, or check seed counts. CX Codex +1 ★ 1,988repo stars setup-ralph setup-ralph lays out Geoffrey Huntley's Ralph Wiggum loop in a directory: file structure, planning and build prompts, and gates that reject bad work. CX Codex +1 ★ 1,988repo stars run-plan run-plan executes a PLAN.md file directly without loading planner skill overhead. It routes tasks to subagents and keeps most of the context window free. CX Codex +1 ★ 1,988repo stars options A command to evaluate multiple options side-by-side: tools, approaches, architectures. It asks clarifying questions, builds a comparison matrix, and recommends the best choice with reasoning. CX Codex +1 ★ 1,988repo stars competitive competitive researches competitors for any feature or product, maps market gaps, and saves a markdown report to your project. CX Codex +1 ★ 1,988repo stars deep-dive deep-dive — a slash command that investigates a topic from several angles and writes a structured report into artifacts/research/ inside your project. CX Codex +1 ★ 1,988repo stars history history — a command to research historical attempts at solving a task: what was tried before, what worked, what mistakes to avoid. Helps prevent repeating errors and apply lessons from experience. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open