- Home
- Skills
- Mosif16
- Codex Skills
- Build Macos Apps
build-macos-apps_skill
- Rust
13
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill mosif16/codex-skills --skill build-macos-apps- .DS_Store6.0 KB
- SKILL.md4.9 KB
Overview
This skill builds professional native macOS apps in Swift using SwiftUI and AppKit from the command line, without Xcode. It covers the full lifecycle: create, debug, test, optimize, and ship apps via CLI tooling and reproducible workflows. The approach is test-driven and outcome-focused: every change is verified and reported. The user describes intent; I implement, verify, and report results.
How this skill works
I run a prescriptive CLI workflow that maps your intent to a concrete sequence of steps (scaffold, build, test, profile, sign, release). After each change I verify with build, test, and launch checks and report concrete outcomes (build success, test counts, app launch). When requirements are unclear I ask clarifying questions before making changes. Tests are added for logic and regressions; UI changes are validated by launching the app.
When to use it
- Start a new macOS app project from the command line without opening an IDE
- Diagnose and fix crashes, build failures, or failing tests in an existing app
- Add a feature or change behavior with incremental, verified steps
- Write tests or run test suites to prove correctness and prevent regressions
- Profile and optimize CPU, memory, or responsiveness issues
- Prepare release artifacts: code signing, notarization, and packaging
Best practices
- Follow small-step workflow: change → verify → report → next change
- Write tests for logic, state changes, bug fixes, and refactors; skip for purely visual exploration
- Always verify builds and tests before committing or moving to the next task
- Ask clarifying questions when requirements are ambiguous or multiple approaches exist
- Leave the repository in a working state at each stopping point (build and tests passing)
Example use cases
- Create a new SwiftUI macOS app scaffolded for documents and persistence, ready to iterate
- Fix a crashing view controller by reproducing the crash in tests and applying a minimal verified fix
- Add a feature such as a menu bar helper or document export with tests and launch verification
- Optimize a slow screen by profiling, fixing hotspots, and measuring before/after improvements
- Package an app for distribution: sign, notarize, and produce release-ready installer artifacts
FAQ
No interactive IDE is required. The workflows use CLI build and test tools so you can work without opening Xcode, though macOS build toolchains are used under the hood.
When will you write tests?
I write tests for logic, state changes, bug fixes, and refactors. I skip tests for rapid visual prototyping unless you ask for test coverage.