example-project
Skill9 starsChanged 6 months agoMITView on GitHub
Use the BazelApp example project for testing XcodeBazelMCP tools end-to-end. Reference when building, running, testing iOS/macOS targets, or validating device and simulator workflows against a real Bazel workspace.
In this repository7 other files it gives its agents.
- cli-developmentSkill
- device-and-uiSkill
- mcp-setupSkill
- simulator-workflowSkill
- swift-agent-debug-logSkill
- tool-handler-developmentSkill
- swift-agent-debug-logSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 73
Before running any build/test tool, set the workspace:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BazelApp Example Project
Location: example_projects/BazelApp/
Quick Reference
| Target | Label | Type | Platform |
| iOS app | //app:app | ios_application | iPhone + iPad |
| macOS app | //mac:mac | macos_application | macOS 14+ |
| API tests | //modules/API:APITests | ios_unit_test | Simulator |
| Models tests | //modules/Models:ModelsTests | ios_unit_test | Simulator |
| macOS tests | //mac:MacTests | macos_unit_test | macOS |
App Identity
Defined in tools/shared.bzl:
- Bundle ID:
com.example.SwiftUIApp - Bundle Name:
SwiftUIApp - Minimum iOS: 18.0
- macOS Bundle ID:
com.example.SwiftUIMacApp - Minimum macOS: 14.0
XcodeBazelMCP Config
example_projects/BazelApp/.xcodebazelmcp/config.yaml defines profiles:
| Profile | Target | Platform | Build Mode |
app | //app:app | simulator | debug |
mac | //mac:mac | macos | debug |
models | //modules/Models:ModelsLib | simulator | none |
mac-tests | //mac:MacTests | macos | debug |
Testing Workflows
Simulator (iOS)
bazel_ios_build_and_run target=//app:app
bazel_ios_test target=//modules/API:APITests
bazel_ios_test target=//modules/Models:ModelsTestsDevice (physical iPhone/iPad)
bazel_ios_device_build_and_run target=//app:app deviceName=iPad
bazel_ios_device_test target=//modules/API:APITests deviceId=<UDID>Device builds use --ios_multi_cpus=arm64. The families field in the iOS target includes both iphone and ipad.
macOS
bazel_macos_build target=//mac:mac
bazel_macos_test target=//mac:MacTests
bazel_macos_run target=//mac:macSetting Workspace
Before running any build/test tool, set the workspace:
bazel_ios_set_workspace workspacePath=<absolute_path>/example_projects/BazelAppOr use the CLI:
xcodebazelmcp mcp --workspace <path>/example_projects/BazelAppProject Structure
BazelApp/
├── app/ # iOS SwiftUI app
│ ├── source/ # MainApp.swift, ContentView.swift
│ ├── Assets/ # App icons, accent color
│ ├── Info.plist
│ ├── ios app.entitlements
│ └── BUILD.bazel # ios_application + swift_library
├── mac/ # macOS SwiftUI app
│ ├── source/ # MacApp.swift, MacContentView.swift
│ ├── Tests/MacTests.swift
│ └── BUILD.bazel # macos_application + macos_unit_test
├── modules/
│ ├── API/ # Shared API library + ios_unit_test
│ └── Models/ # Shared Models library + ios_unit_test
├── tools/
│ ├── shared.bzl # Bundle IDs, version constants
│ ├── repositories.bzl # External dependencies
│ └── extensions.bzl # Bzlmod extensions
├── .xcodebazelmcp/config.yaml # MCP profiles
├── .bazelrc # Build flags, remote cache config
├── .bazelversion # Bazel version pin
├── MODULE.bazel # Bzlmod deps (rules_apple 4.2.0, rules_swift 3.1.2)
└── BUILD.bazel # xcodeproj generator + lint genruleDependencies (MODULE.bazel)
rules_apple4.2.0rules_swift3.1.2rules_xcodeproj3.2.0apple_support1.23.1
Notes
.bazelrchardcodes--ios_simulator_version=18.5for CI — override withsimulatorVersionparam oruser.bazelrc.- Device builds require code signing — for local dev Bazel uses automatic signing. For CI, provisioning profiles must be configured in the build rules.
- The
//app:apptarget supports both iPhone and iPad families. xcodeprojgenerator target (:xcodeproj) creates an Xcode project for IDE integration.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

