xcode27-skills: Apple's Xcode 27 agent skills, repackaged for Claude Code and Codex

What is in the box

Seven skills, each a top-level directory. swiftui-specialist covers idiomatic SwiftUI: structure, data flow, environment, modifiers, localization, animations, ForEach and soft-deprecated APIs. swiftui-whats-new-27 covers new SwiftUI APIs, behaviours and deprecations in the 2027 OS releases across iOS, macOS, watchOS, tvOS and visionOS, naming the @State macro, reorderable, swipe actions, toolbar overflow, AsyncImage, item bindings and document-based apps. uikit-app-modernization is about multi-window environments: replacing legacy shared-state APIs, migrating to the scene lifecycle, supporting dynamic scene sizing.

test-modernizer moves test suites onto modern Swift Testing features or migrates them off XCTest. c-bounds-safety documents the C -fbounds-safety language extension, its pointer annotations, adoption path, build settings and runtime debugging. audit-xcode-security-settings audits and progressively enables security-oriented build settings, covering compiler warnings, static analyzer checkers and Enhanced Security hardening. device-interaction verifies iOS app behaviour on a device or simulator through screenshots, the UI hierarchy and touch interactions.

The attribution, and the licence question it raises

The README is unusually clear about provenance. The content was authored and published by Apple and exported from Xcode 27. The repository is a redistribution for convenience and reference only, all rights to the underlying guidance belong to Apple, and no licence over Apple content is granted by the repository.

That is the single most important fact for anyone deciding to adopt it. The repository itself declares no licence, so the directory layout and the README carry no grant, and the SKILL.md files inside are Apple material. Treat it as a convenience copy of documentation rather than an asset you can ship under your own terms.

Installing with npx skills

Each top-level directory is self-contained, so you can install all seven or pick one.

# Pick interactively from the list of skills:
npx skills add superagents-lab/xcode27-skills

# Install one specific skill:
npx skills add superagents-lab/xcode27-skills --skill swiftui-specialist

# Install all seven:
npx skills add superagents-lab/xcode27-skills --skill '*'

The skills CLI auto-detects your agent, covering Claude Code and Codex, and installs into it. Useful flags are --list to preview the skills without installing, -g or --global to install at the user level instead of into the current project, and --copy to copy files instead of symlinking. Node is required, and the README suggests brew install node if npx is missing.

Installing by hand, and what a skill actually is

A skill is just a directory containing a SKILL.md, so any agent supporting the Agent Skills format can use one:

git clone https://github.com/superagents-lab/xcode27-skills.git

# Copy all seven skills, or just the ones you want, into your agent's skills directory:
cp -R xcode27-skills/*/ <your-skills-directory>/
cp -R xcode27-skills/swiftui-specialist <your-skills-directory>/

The agent auto-discovers any directory containing a SKILL.md and surfaces it when a task matches that skill description. Each one holds a SKILL.md with YAML frontmatter carrying name and description, plus optional references and scripts subdirectories that the agent loads on demand.

How the agent decides to use one

Once installed, no explicit invocation is needed. The agent surfaces a skill automatically when your request matches its description field. In Claude Code you can also trigger one by name, for example /swiftui-specialist, and add focus hints such as check for soft-deprecated APIs or modernize these XCTest cases.

That is the practical argument for installing only what you need rather than all seven. The description field is the trigger, so a broad installation means more chances for the agent to load Apple guidance into a task where it does not apply.

Where this helps and where it does not

The value is provenance. An agent asked about SwiftUI structure is otherwise working from training data that predates the API it is being asked about, and the 2027 release notes and the -fbounds-safety extension are exactly the kind of material that drifts. A skill directory loaded on demand gives the agent current text to read.

The limits follow from what this is. It is guidance text, not a linter and not a compiler diagnostic. audit-xcode-security-settings can tell the agent which build settings to enable, but it does not run your build, and device-interaction needs a device or simulator to look at. The repository declares no releases either, so there is no version tag to pin to.

Maintenance and what to verify before adopting it

The last push was on 2026-06-09. The repository declares no licence, and the skills themselves are Apple content exported from Xcode 27.

Decide two things before adopting it. Whether your agent supports the Agent Skills format, since that is the only mechanism here. And whether you are comfortable loading Apple authored guidance into a project whose licensing review has not seen it, because the repository is explicit that it grants no rights over that content. Run npx skills add superagents-lab/xcode27-skills --list first and read the list before installing anything.

Editorial conclusion

Install xcode27-skills if your agent writes Swift and you would rather it read current Apple guidance than recall API shapes, and install only the directories you actually need. Skip it if you want enforcement rather than guidance, since these are documents the agent reads and not checks it runs, and do not redistribute it, because the repository states that all rights belong to Apple and grants no licence over the content. Verify with npx skills add superagents-lab/xcode27-skills --list, then confirm which skill directory your agent actually picked up.

Frequently asked questions

Official sources

1. Issues
2. README
3. superagents-lab/xcode27-skills on GitHub