Setup
Shpigford/chops
Get a new developer up and running with the Chops codebase — prerequisites, build, architecture, and common tasks.
Build professional native macOS apps in Swift with SwiftUI and AppKit.
Install Build macOS Apps
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/taches-cc-resources build-macos-apps --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/expertise/macos-apps .claude/skills/build-macos-apps && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .claude/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-appsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/taches-cc-resources build-macos-apps --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/expertise/macos-apps .agents/skills/build-macos-apps && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .agents/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/taches-cc-resources build-macos-apps --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/expertise/macos-apps .cursor/skills/build-macos-apps && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .cursor/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/glittercowboy/taches-cc-resources.git --path skills/expertise/macos-apps--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/taches-cc-resources build-macos-apps --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/expertise/macos-apps .gemini/skills/build-macos-apps && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .gemini/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install glittercowboy/taches-cc-resources build-macos-appsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/expertise/macos-apps .github/skills/build-macos-apps && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .github/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glittercowboy/taches-cc-resources build-macos-apps --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/expertise/macos-apps .opencode/skills/build-macos-apps && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-macos-apps" agent skill from https://github.com/glittercowboy/taches-cc-resources/tree/main/skills/expertise/macos-apps into .opencode/skills/build-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-macos-apps", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-macos-apps- GitHub stars
- 2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 566 words
- Files
- 27 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build professional native macOS apps in Swift with SwiftUI and AppKit.
- Works in 6 steps: Prove, Don't Promise → Tests for Correctness, Eyes for Quality → Report Outcomes, Not Code → …
- Tasks that involve iOS development
- SKILL.md covers How We Work, After Every Change, Testing Decision and Domain Knowledge, plus 1 more section
- Calls xcodebuild
What it does
Build macOS Apps is an agent skill from glittercowboy/taches-cc-resources. Build professional native macOS apps in Swift with SwiftUI and AppKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 27 other files, including reference files (for example `references/app-architecture.md`, `references/app-extensions.md` and `references/appkit-integration.md`).
It sits in Mobile, covering iOS development. It works with macOS, Xcode and SwiftUI. The repository describes itself as: A collection of my favorite custom Claude Code resources to make life easier. The licence is MIT.
When your agent uses it
- Tasks that involve iOS development
Example prompts
- “/build-macos-apps”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1757615. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
xcodebuild
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Build macOS Apps loads about 1.2k tokens when it runs, and up to ~64k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 566 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from glittercowboy/taches-cc-resources at commit 1757615, republished under its MIT licence (© glittercowboy). 566 words, ~1,249 tokens.
Download SKILL.mdSave it as
.claude/skills/build-macos-apps/SKILL.md (or your agent's skills folder). This skill also uses 26 other files; get the full folder from GitHub.- 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:
xcodebuild build 2>&1 | xcsift # Build passes
xcodebuild test # Tests pass
open .../App.app # App launchesIf 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 changeNever 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?
- Build a new app
- Debug an existing app
- Add a feature
- Write/run tests
- Optimize performance
- Ship/release
- 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>
Show full SKILL.md (199 more words)Show less
After Every Change
# 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.appReport 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> |
© glittercowboy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 26 other files (references) in skills/expertise/macos-apps of glittercowboy/taches-cc-resources.
- SKILL.md
- references/app-architecture.md
- references/app-extensions.md
- references/appkit-integration.md
- references/cli-observability.md
- references/cli-workflow.md
- references/concurrency-patterns.md
- references/data-persistence.md
- references/design-system.md
- references/document-apps.md
- references/macos-polish.md
- references/menu-bar-apps.md
- references/networking.md
- references/project-scaffolding.md
- references/security-code-signing.md
- references/shoebox-apps.md
- references/swiftui-patterns.md
- references/system-apis.md
- references/testing-debugging.md
- references/testing-tdd.md
- … and 7 more
Open the folder on GitHubat commit 1757615
Compare with similar skills
Build macOS Apps next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Build macOS Apps this skillglittercowboy/taches-cc-resources | 2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| SetupShpigford/chops | 1.9k | — | ~980 | Automated safety check: Pass | Custom licence | |
| SwiftUI Design SkillWholiver/swiftui-design-skill | 204 | — | ~2.8k | Automated safety check: Pass | MIT | |
| FlowdeckSwiftedMind/Tessera | 116 | — | ~11k | Automated safety check: Pass | MIT | |
| macOS Menubar Tuist AppDimillian/Skills | 4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Bootstrap iOSRayFernando1337/rayfernando-skills | 130 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
SwiftUI Design Skill
Wholiver/swiftui-design-skill
Guides the agent to design distinctive SwiftUI interfaces for iOS and macOS, with six anti-generic rules, a design direction workflow and a five-dimension review.
Flowdeck
SwiftedMind/Tessera
FlowDeck is REQUIRED for all Apple platform build/run/test/launch/debug/simulator/device/log/automation tasks.
macOS Menubar Tuist App
Dimillian/Skills
Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI.
Bootstrap iOS
RayFernando1337/rayfernando-skills
Bootstrap agents for iOS, iPadOS, macOS, Swift, SwiftUI, SwiftData/Core Data, Swift Testing, Xcode build/test/debug, Simulator, App Intents, or XcodeBuildMCP work.
Xcstrings Manager
Eslzzyl/Pixiv-SwiftUI
Manage Xcode String Catalog (.xcstrings) localization files through a command-line interface.
More from glittercowboy/taches-cc-resources
All 12 skills in this repoCreate MCP Servers
glittercowboy/taches-cc-resources
Create Model Context Protocol (MCP) servers that expose tools, resources, and prompts to Claude.
The Pirate Bay
glittercowboy/taches-cc-resources
Search The Pirate Bay for torrents and extract magnet links via the apibay.org JSON API.
Create Plans
glittercowboy/taches-cc-resources
Create hierarchical project plans optimized for solo agentic development.
Create Agent Skills
glittercowboy/taches-cc-resources
Expert guidance for creating, writing, building, and refining Claude Code Skills.
Create Hooks
glittercowboy/taches-cc-resources
Expert guidance for creating, configuring, and using Claude Code hooks.
Create Meta Prompts
glittercowboy/taches-cc-resources
Create optimized prompts for Claude-to-Claude pipelines with research, planning, and execution stages.
Related
Categories
Questions about Build macOS Apps
What does Build macOS Apps do?
Build professional native macOS apps in Swift with SwiftUI and AppKit. Build macOS Apps is an agent skill from glittercowboy/taches-cc-resources. Build professional native macOS apps in Swift with SwiftUI and AppKit.
When should I use Build macOS Apps?
Build macOS Apps fits situations like: tasks that involve iOS development.
How do I install Build macOS Apps in Claude Code?
Run `npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a claude-code`. Or copy the skill folder (skills/expertise/macos-apps in glittercowboy/taches-cc-resources) into .claude/skills/build-macos-apps in your project. Claude Code loads it when a task matches its description.
How do I install Build macOS Apps in Codex?
Run `npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a codex`. Or copy the skill folder (skills/expertise/macos-apps in glittercowboy/taches-cc-resources) into .agents/skills/build-macos-apps in your project. Codex loads it when a task matches its description.
Can I use Build macOS Apps in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glittercowboy/taches-cc-resources --skill build-macos-apps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-macos-apps, .gemini/skills/build-macos-apps, .github/skills/build-macos-apps and .opencode/skills/build-macos-apps in your project.
What does Build macOS Apps need to run?
Going by SKILL.md and its folder, Build macOS Apps needs the command-line tools its instructions call (xcodebuild).
Does Build macOS Apps access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Build macOS Apps safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Build macOS Apps use?
Build macOS Apps is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Build macOS Apps use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 63k tokens, read only when the agent opens those files.
What are the alternatives to Build macOS Apps?
Skills that share tags, products or a category with Build macOS Apps: Setup (Shpigford/chops, 1.9k stars), SwiftUI Design Skill (Wholiver/swiftui-design-skill, 204 stars), Flowdeck (SwiftedMind/Tessera, 116 stars) and macOS Menubar Tuist App (Dimillian/Skills, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Build macOS Apps?
glittercowboy (a GitHub user) maintains it in glittercowboy/taches-cc-resources, which has 1,980 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on April 1, 2026.
Source: glittercowboy/taches-cc-resources on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.