Build forager with the correct Xcode configuration. Uses iPhone 17 Pro simulator. Filters output for errors and warnings. TRIGGER when the user says \"build it\", \"build the app\", \"run a build\", \"compile\", \"does it build\", \"rebuild\", \"try building\", \"does it compile\", or any request to build or compile the project.
Installs into .claude/skills of the current project.
Are you the author of Build?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/rfhayn-build)
---
name: build
description: "Build forager with the correct Xcode configuration. Uses iPhone 17 Pro simulator. Filters output for errors and warnings. TRIGGER when the user says \"build it\", \"build the app\", \"run a build\", \"compile\", \"does it build\", \"rebuild\", \"try building\", \"does it compile\", or any request to build or compile the project."
---
# Build Forager
Build the project with the correct configuration.
## Build Command
Run the build script (executes without loading source into context):
```bash
.claude/skills/build/scripts/build.sh /Users/rich/Development/forager
```
Or run directly:
```bash
xcodebuild -project forager.xcodeproj -scheme forager -destination 'platform=iOS Simulator,name=iPhone 17 Pro' build 2>&1 | grep -E "BUILD|error:|warning:" | head -30
```
## Configuration
- **Simulator**: iPhone 17 Pro (not iPhone 16 Pro — it's unavailable)
- **Scheme**: forager
- **iOS target**: 26+
- **CloudKit**: DISABLED in DEBUG, ENABLED in Release
## On Build Failure
If the build fails:
1. Read the full error output
2. Check if it's a compilation error, dependency error, or configuration error
3. For >5 consecutive build errors, stop and reassess approach (quality gate)
## On Build Success
Report:
- BUILD SUCCEEDED
- Number of warnings (if any)
- Build time
## Notes
- The `-quiet` flag suppresses output; avoid it when debugging
- `CURRENT_PROJECT_VERSION` is managed by the user — never modify build numbers
