mcpbeat Sign in

Bootstrap Ios Agent Skill

Bootstrap agents for iOS, iPadOS, macOS, Swift, SwiftUI, SwiftData/Core Data, Swift Testing, Xcode build/test/debug, Simulator, App Intents, or XcodeBuildMCP work. Use before building, fixing, refactoring, QAing, or setting up Apple-platform repos, and when asked to load/install Ray's iOS skills or bootstrap iOS.

6k tokens
context cost
the whole folder, loaded on every use
7
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
116
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/RayFernando1337/rayfernando-skills --skill bootstrap-ios

What comes with it

18 730 bytes besides the instruction
references/install-and-bootstrap.md
references/skill-map.md
references/sources.md
references/workflow.md
references/xcodebuildmcp.md
scripts/bootstrap-ios-skills.sh

The instruction itself

6 sections, as written by the author

Bootstrap iOS

Use this as the single entry point before touching an Apple-platform app.

It is a router skill: discover the project, load only the references needed

for the current job, verify that build/test tools exist, then act.

The default posture is conservative:

  • Build and test before judging code.
  • Prefer modern Swift, SwiftUI, Observation, Swift Concurrency, Swift Testing,

SwiftData, and current Xcode APIs.

  • Avoid deprecated APIs unless the deployment target requires them.
  • Use XcodeBuildMCP or an agent-friendly build script instead of raw,

unfiltered xcodebuild output when possible.

  • Load focused skill packs on demand. Do not dump every Swift rule into context.

First move

  • Detect surfaces: iOS, iPadOS, macOS, mixed web/native, SwiftPM, Xcode

project/workspace, Tuist, XcodeGen, CocoaPods, or buildable folders.

  • Read references/workflow.md.
  • If the task involves setup or machine bootstrap, read

references/install-and-bootstrap.md.

  • If the task involves building, running, simulator, tests, or debugging,

read references/xcodebuildmcp.md.

  • Pick only the external skill packs relevant to the current task from

references/skill-map.md.

Mode picker

| User asks for... | Load |

|---|---|

| "Bootstrap iOS", "install my iOS skills", "one command" | install-and-bootstrap.md |

| Build, test, simulator, logs, debug, device install | xcodebuildmcp.md |

| SwiftUI screen, navigation, sheets, app wiring | skill-map.md SwiftUI entries |

| Animation, motion, "make it feel alive", loaders, delight | Also use swiftui-animation-match (interaction-to-animation matcher) |

| Async/await, actors, Sendable, Swift 6 migration | skill-map.md concurrency entries |

| Unit tests, Swift Testing, XCTest migration | skill-map.md testing entries |

| SwiftData, models, queries, migrations, CloudKit | skill-map.md SwiftData entries |

| Core Data stack, fetches, background contexts | skill-map.md Core Data entries |

| Slow builds, compiler time, project settings | SwiftLee Xcode Build Optimization in skill-map.md |

| Architecture/rules loader/advanced Swift discipline | Merowing rules in skill-map.md |

| App Intents, Siri, Shortcuts, widgets | Official Build iOS Apps plugin notes in skill-map.md |

| QA this iOS app | Also use running-bug-review-board and its iOS simulator playbook |

When installing external skills

Do not silently modify the user's machine. If the user asks to install or

bootstrap, explain what will be installed, then use the helper script in dry-run

first:

bash scripts/bootstrap-ios-skills.sh --dry-run --agent cursor

After the user confirms, run without --dry-run. The helper is idempotent and

keeps optional/non-GitHub sources as instructions instead of pretending it can

install them. After a real install it verifies every expected skill actually

landed and is complete (every references/, scripts/, and assets/ file

cited by each SKILL.md exists on disk) and fails loudly with reinstall

instructions if any skill is missing entirely or installed shallow. See

references/install-and-bootstrap.md.

Verification

Before reporting an Apple-platform task done:

  • Confirm the scheme/project/workspace you used.
  • Run the smallest meaningful build or test command.
  • Capture build errors from clean output, not raw wall-of-text logs.
  • If using XcodeBuildMCP, name the tool/command used.
  • If build/test is blocked by signing, missing simulator, or missing Xcode,

report the blocker with the exact next command to fix it.

  • For UI work, run in Simulator when feasible and capture enough evidence for

the next agent to verify.

Sources

This skill synthesizes Paul Solt's X article "Install These Skills Before Codex

Touches Your Xcode Project", the linked community skill repos, official OpenAI

plugin references, Merowing rules, AppCreator notes, and getsentry/XcodeBuildMCP.

See references/sources.md.

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take rayfernando1337/bootstrap-ios from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.