agentleFS
DebugSwiftDebugSwift/XcodeBazelMCP/.agents/skills/example-project/SKILL.md

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.

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
  1. Distinctive:

    Before running any build/test tool, set the workspace:

    line 73

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BazelApp Example Project

Location: example_projects/BazelApp/

Quick Reference

TargetLabelTypePlatform
iOS app//app:appios_applicationiPhone + iPad
macOS app//mac:macmacos_applicationmacOS 14+
API tests//modules/API:APITestsios_unit_testSimulator
Models tests//modules/Models:ModelsTestsios_unit_testSimulator
macOS tests//mac:MacTestsmacos_unit_testmacOS

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:

ProfileTargetPlatformBuild Mode
app//app:appsimulatordebug
mac//mac:macmacosdebug
models//modules/Models:ModelsLibsimulatornone
mac-tests//mac:MacTestsmacosdebug

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:ModelsTests

Device (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:mac

Setting Workspace

Before running any build/test tool, set the workspace:

bazel_ios_set_workspace  workspacePath=<absolute_path>/example_projects/BazelApp

Or use the CLI:

xcodebazelmcp mcp --workspace <path>/example_projects/BazelApp

Project 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 genrule

Dependencies (MODULE.bazel)

  • rules_apple 4.2.0
  • rules_swift 3.1.2
  • rules_xcodeproj 3.2.0
  • apple_support 1.23.1

Notes

  • .bazelrc hardcodes --ios_simulator_version=18.5 for CI — override with simulatorVersion param or user.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:app target supports both iPhone and iPad families.
  • xcodeproj generator target (:xcodeproj) creates an Xcode project for IDE integration.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.