/swiftui-skills

Apple-authored SwiftUI and Apple platform guidance, packaged as skills for AI coding agents.

What is this?

SwiftUI is opinionated. Most AI agents do not know those opinions.

/swiftui-skills extracts internal Apple documentation shipped inside Xcode and turns it into reusable skills that help AI agents write idiomatic, Apple-native SwiftUI code.

• Uses Apple-written guidance from inside Xcode
• Reduces hallucinated or non-idiomatic SwiftUI
• Works with Claude Code, Cursor, Codex, OpenClaw, and similar tools
• Ships native plugin manifests for Claude Code, Cursor, and Codex
• Open source and local-first

Installation

Installation differs a bit by harness. If you use more than one, keep the shared payload the same and choose the install surface that fits that tool.

Direct install (Recommended)

curl -fsSL https://swiftui-skills.ameyalambat.com/install | bash

The installer extracts local Xcode docs and installs the skill into detected runtimes, including OpenClaw shared installs at ~/.openclaw/skills/swiftui-skills.

You can also use the skills TUI:

npx skills add ameyalambat128/swiftui-skills

Choose the install scope in the skills TUI and keep Symlink (Recommended) selected.

Shared agent install

~/.agents/skills/swiftui-skills/setup.sh

Project-local agent install

./.agents/skills/swiftui-skills/setup.sh

Claude Code

This repo ships a native Claude Code plugin manifest at ./.claude-plugin/plugin.json.

For local plugin testing, symlink the repo into a Claude skills directory and start a new session:

ln -s /absolute/path/to/swiftui-skills ~/.claude/skills/swiftui-skills-plugin

Cursor

This repo ships a native Cursor plugin manifest at ./.cursor-plugin/plugin.json.

For local plugin testing, symlink the repo into Cursor’s local plugins directory and reload the window:

mkdir -p ~/.cursor/plugins/local
ln -s /absolute/path/to/swiftui-skills ~/.cursor/plugins/local/swiftui-skills

Codex

This repo ships a native Codex plugin manifest at ./.codex-plugin/plugin.json.

Codex plugin packaging is included here so the repo is plugin-ready, but marketplace distribution is still optional. The direct skill install remains the simpler path today.

OpenClaw manual install

OpenClaw can load the same canonical skill package from any of these paths:

• ~/.agents/skills/swiftui-skills
• ~/.openclaw/skills/swiftui-skills
• /skills/swiftui-skills

For a shared OpenClaw install:

mkdir -p ~/.openclaw/skills
cp -R skills/swiftui-skills ~/.openclaw/skills/swiftui-skills
~/.openclaw/skills/swiftui-skills/setup.sh

For a workspace-local OpenClaw install:

mkdir -p ./skills
cp -R skills/swiftui-skills ./skills/swiftui-skills
./skills/swiftui-skills/setup.sh

After setup, start a new OpenClaw session or restart the gateway.

Requirements

• macOS
• Xcode 26 or later

Custom paths

If Xcode is installed in a non-standard location:

# Custom Xcode location
bash src/scripts/install.sh --xcode-path /Applications/Xcode-beta.app

# Direct path to docs folder
bash src/scripts/install.sh --docs-path /path/to/AdditionalDocumentation

How it works

1. The installer extracts Apple documentation from your local Xcode install.
2. The skill tells the agent how to use that documentation during generation and review.
3. Your agent uses the extracted docs as source of truth when writing SwiftUI code.

No Apple documentation is redistributed. Everything is extracted locally during setup.

What “supports OpenClaw” means

This project is still a developer-focused SwiftUI skill.

OpenClaw support means:

• The canonical SKILL.md is compatible with OpenClaw skill loading.
• The same skill package can live in OpenClaw-visible paths like ~/.agents/skills, ~/.openclaw/skills, or /skills.
• OpenClaw users get the same local-docs workflow after running setup.sh.
• OpenClaw users can verify the skill with native commands like openclaw skills list.

This does not add a plugin, split the package, or change the product into an OpenClaw-only tool.

What’s included

Documentation extracted from Xcode covers:

• SwiftUI patterns and composition
• App Intents and system integrations
• AlarmKit integration
• StoreKit updates
• WebKit + SwiftUI integration
• SwiftData inheritance
• Swift Concurrency updates
• Liquid Glass design (SwiftUI, UIKit, AppKit, WidgetKit)
• Widgets for visionOS
• Low-level Swift performance primitives (InlineArray, Span)

Usage

Claude Code and similar agents

The installer can place the skill directly into detected agent paths like ~/.claude/skills, ~/.codex/skills, and related runtimes.

The repo root also carries native plugin manifests for Claude Code, Cursor, and Codex, while the canonical skill payload now lives at skills/swiftui-skills/.

OpenClaw

OpenClaw already loads visible skills from these paths, in precedence order:

1. /skills
2. /.agents/skills
3. ~/.agents/skills
4. ~/.openclaw/skills

To verify the skill is visible:

openclaw skills list

Then start a new session and try a representative SwiftUI task:

openclaw agent --message "Build a SwiftUI settings screen with a toolbar and explain which local docs you used."

Expected smoke-test behavior:

• The skill is listed by OpenClaw.
• The agent references local extracted docs instead of inventing APIs.
• If docs/ is empty, the agent tells you to run setup.sh before proceeding.

Project structure

swiftui-skills/
├── .claude-plugin/
│   └── plugin.json            # Claude Code plugin manifest
├── .codex-plugin/
│   └── plugin.json            # Codex plugin manifest
├── .cursor-plugin/
│   └── plugin.json            # Cursor plugin manifest
├── skills/
│   └── swiftui-skills/        # Canonical shared skill payload
│       ├── SKILL.md           # Canonical skill contract
│       ├── manifest.json      # Tool compatibility helpers
│       ├── prompts/           # System, router, reviewer, generator, refactorer
│       ├── docs/              # Populated by setup
│       └── setup.sh           # Local Xcode docs extraction
├── src/
│   ├── app/                   # Next.js website
│   └── scripts/
│       ├── install.sh
│       └── uninstall.sh
└── public/
    └── install                # curl target

Uninstall

bash src/scripts/uninstall.sh

Who this is for

• iOS developers refactoring into SwiftUI
• Developers using AI to write SwiftUI-heavy apps
• People working with App Intents, StoreKit, Widgets, or visionOS
• Anyone tired of fighting non-idiomatic AI-generated SwiftUI

Star History

License

MIT

Author

Built by Ameya Lambat. Not affiliated with Apple.