iOS/macOS projects rely heavily on xcodebuild for compilation, testing, archiving, and code signing. These commands produce extremely verbose output that would benefit significantly from RTK's token-optimized filtering.
Suggested commands
xcodebuild build — build a project/workspace
xcodebuild test — run unit and UI tests
xcodebuild archive — create an archive for distribution
xcodebuild clean — clean build artifacts
xcodebuild -showBuildSettings — display build settings
xcodebuild -list — list schemes, targets, and configurations
xcodebuild build-for-testing / xcodebuild test-without-building — split build and test phases
xcodebuild -exportArchive — export an archive to IPA/PKG
xcodebuild is notoriously verbose — a typical build can produce thousands of lines of output, most of which is redundant for an LLM context window. Filtering down to warnings, errors, and build results would yield massive token savings.
iOS/macOS projects rely heavily on xcodebuild for compilation, testing, archiving, and code signing. These commands produce extremely verbose output that would benefit significantly from RTK's token-optimized filtering.
Suggested commands
xcodebuild build— build a project/workspacexcodebuild test— run unit and UI testsxcodebuild archive— create an archive for distributionxcodebuild clean— clean build artifactsxcodebuild -showBuildSettings— display build settingsxcodebuild -list— list schemes, targets, and configurationsxcodebuild build-for-testing/xcodebuild test-without-building— split build and test phasesxcodebuild -exportArchive— export an archive to IPA/PKGxcodebuild is notoriously verbose — a typical build can produce thousands of lines of output, most of which is redundant for an LLM context window. Filtering down to warnings, errors, and build results would yield massive token savings.