xcode-makefiles
Install strict Xcode Makefile tooling for iOS/macOS projects, including build/run/test scripts with AGENT_NAME-based per-agent isolation under build/. Use when a project needs reproducible local CLI builds without full app scaffolding.
git clone --depth 1 https://github.com/robertguss/claude-code-toolkit /tmp/xcode-makefiles && cp -r /tmp/xcode-makefiles/skills/mobile-app-dev/ios-mac-app-creator/xcode-makefiles ~/.claude/skills/xcode-makefilesSKILL.md
# Xcode Makefiles ## Overview Paul Solt Paul@SuperEasyApps.com Version: 0.9.8 Install a focused Makefile + scripts toolkit into an existing or newly scaffolded Xcode project. Canonical conventions: - `AGENT_NAME` is the only agent env var. - Per-agent paths live under `build/`: - `build/DerivedData/<AGENT_NAME>` - `build/logs/<AGENT_NAME>` - `build/cache/<AGENT_NAME>` - `build/tmp/<AGENT_NAME>` ## Install ```bash skills/xcode-makefiles/scripts/install.sh \ --project-dir /path/to/project \ --app-name WalkTrack \ --platform ios ``` Common flags: - `--project-dir PATH` required - `--mode install|upgrade` default `install` - `--dry-run` preview changes only Toolkit flags: - `--app-name NAME` required - `--platform ios|macos` required - `--sim-name NAME` optional, defaults to `auto` for iOS - `--namespace NAME` optional, installs `Makefile.NAME` and `scripts/NAME/` Installed scripts include: - `scripts/atomic_commit.sh` - `scripts/xcbuild.sh` - `scripts/resolve_agent_name.sh` - `scripts/resolve_sim_destination.sh` - `scripts/diagnose.sh` - `scripts/run_app_macos.sh` - `scripts/run_app_ios_sim.sh` - `scripts/clean.sh` - `scripts/move_to_trash.sh` ## Targets Installed Make targets are intentionally minimal: - `make diagnose` - `make build` - `make test` - `make run` - `make build-and-run` - `make build-and-run-background` - `make clean` - `make agent-verify`
Guide for creating effective skills. This skill should be used when users want
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles, business content, manifestos, or any prose requiring a clear, punchy, opinionated style.
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when users provide sample text and want to capture the voice for future use.
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.
Collaborative brainstorming partner for multi-session ideation projects. Use