swiftui-skills
A skill that gives the agent Apple's own SwiftUI guidance, which the installer extracts from your local Xcode
- 125 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The main install command downloads and immediately runs a script from the author's site
- The installer writes files into the skill directories of every detected agent
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/swiftui-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The main install command downloads and immediately runs a script from the author's site
- The installer writes files into the skill directories of every detected agent
This is third-party code. Review the repository files before installing.
What it does
The swiftui-skills installer reads the AdditionalDocumentation shipped inside Xcode 26 and later and places it in the skill's `docs/` folder on your machine. The author does not redistribute Apple's material: the folder in the repository is empty, and the text appears only after `setup.sh` runs. SKILL.md requires the agent to ground every API claim in those files. To write code, the agent picks the relevant documents, notes the applicable rules briefly and only then produces code that compiles. When reviewing, it lists problems and cites the documents used. If unsure, it asks at most one question, and only when the answer changes the architecture. Prompts for a router, reviewer, generator and refactorer sit alongside. The documentation covers SwiftUI patterns, App Intents, AlarmKit, StoreKit, WebKit in SwiftUI, SwiftData inheritance, Swift Concurrency updates, Liquid Glass for SwiftUI, UIKit, AppKit and WidgetKit, visionOS widgets, and InlineArray and Span.
Who it is for. iOS developers moving an app to SwiftUI or writing one with an agent who are tired of fixing outdated and invented API calls.
Good fit when
- The agent produces SwiftUI code with modifiers that do not exist and has to be tied to Apple documentation
- The project adds App Intents, widgets or AlarmKit, which the model knows little about
- A screen is moving to Liquid Glass and must be checked against Apple's guidance for SwiftUI, UIKit and AppKit
- An agent reviews a SwiftUI module and every remark has to cite a document
Not a fit when
- The project is built off macOS or without Xcode 26: the installer takes documentation only from a local Xcode
- The task is general Swift technique without SwiftUI, such as concurrency or architecture: other skills in the catalog fit better
- Piping a script into the terminal is banned by security policy: the main install route here is `curl | bash`
Example request
Build a SwiftUI settings screen with a toolbar and explain which local docs you usedLimitations
Runs on macOS and needs Xcode 26 or later. The documentation is not in the repository: `setup.sh` extracts it from your Xcode, and without that step the `docs/` folder is empty, so the agent has to say setup must be run. The main install command downloads and executes a script from the author's site. The project is not affiliated with Apple. OpenClaw support only means the same SKILL.md loads from shared directories; there is no separate plugin for it. The last commit was made in July 2026.
How to disable. Run `bash src/scripts/uninstall.sh` from the repository clone or delete the `swiftui-skills` folder from `~/.claude/skills`, `~/.codex/skills` or `~/.agents/skills`.
FAQ
How do I install swiftui-skills in Claude Code?
Run `curl -fsSL https://swiftui-skills.ameyalambat.com/install | bash`: the installer finds Xcode, extracts the documentation and places the skill in the directories of detected agents, including `~/.claude/skills`. The same skill installs through `npx skills add ameyalambat128/swiftui-skills`.
What if Xcode is not in the default location?
Pass the path with a flag: `bash src/scripts/install.sh --xcode-path /Applications/Xcode-beta.app`. If you know the documentation folder, give it through `--docs-path`.
Does the project redistribute Apple documentation?
No, the materials are extracted locally during installation and stay on your machine. The repository holds an empty `docs/` folder with a `.gitkeep` file.
Does the skill work with Cursor and Codex?
Yes, the repository ships plugin manifests for Claude Code, Cursor and Codex, and the installer places the skill in the directories of detected agents. For Codex the author calls direct skill install the simpler route compared to the plugin.
How do I uninstall swiftui-skills?
Run `bash src/scripts/uninstall.sh` from the repository clone. You can also delete the skill folder from the agent directory by hand, for example `~/.claude/skills/swiftui-skills`.
Discussion
No questions or reviews yet.
Related
SkillsSkills for Apple development: SwiftUI, UIKit and Liquid Glass references, Swift 6 guides and a router for iOS 26+ tasks
A set of skills for iOS 26+, Swift 6.3 and SwiftUI that gives the agent knowledge of modern Apple frameworks
A SwiftUI best practices skill: state, view composition, performance, new APIs, Liquid Glass and Instruments trace analysis
SwiftUI Design Skill
swiftui-design-skill
A SwiftUI interface design skill: compilable code, tokens, patterns and six rules against AI sloppiness. One-command installation through npx skills
Two SwiftUI skills: native Liquid Glass for iOS 26 and adaptive layout for the foldable iPhone Duo with no separate app version
Paul Hudson's skill for reviewing and writing SwiftUI for iOS 26: deprecated APIs, data flow, navigation, accessibility, performance
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| swiftui-skills (this card) | no | 125 | |
| SwiftUI Expert Skill | no | 3,830 | ships its own rules and SwiftUI code reviews and does not use Apple documentation from Xcode |
| SwiftUI Pro | no | 6,479 | reviews SwiftUI code for modern APIs and performance against its own rule list |
README in short
Installation is laid out per agent, an OpenClaw smoke test, system requirements and uninstall steps. A separate section explains what OpenClaw support means: the same SKILL.md loads from shared paths and the package does not turn into a plugin.
README badge
Original SKILL.md
---
name: swiftui-skills
description: Apple-authored SwiftUI and platform guidance extracted from Xcode. Helps AI agents write idiomatic, Apple-native SwiftUI with reduced hallucinations.
metadata:
openclaw:
os: ["darwin"]
requires:
bins: ["xcodebuild"]
---
# swiftui-skills
## What this is
A packaged set of Apple-authored AdditionalDocumentation shipped inside Xcode, plus prompts that enforce Apple-native patterns and reduce hallucinations for developer-focused coding workflows.
## Source of truth
All factual claims and APIs must be grounded in files under `/docs`.
## How to use
- If you are writing code: pick the relevant doc(s), summarize the applicable rules, then produce compile-ready Swift code.
- If you are reviewing code: list issues and improvements, referencing doc(s) used.
- If uncertain: ask at most 1 question, only if the answer changes architecture.
## Setup check
If the `docs/` folder is empty or contains no `.md` files, the Xcode documentation has not been extracted yet.
Tell the user to run the setup script from the installed skill directory:
```
# Shared agent install
~/.agents/skills/swiftui-skills/setup.sh
# OpenClaw shared install
~/.openclaw/skills/swiftui-skills/setup.sh
# OpenClaw workspace install
./skills/swiftui-skills/setup.sh
# Project-local agent install
./.agents/skills/swiftui-skills/setup.sh
```
Do not proceed with SwiftUI guidance until docs are available.
## Non-negotiables
- Do not invent types or APIs. If it is not in `/docs`, say so and offer a safe alternative.
- Prefer minimal, idiomatic SwiftUI and platform conventions.
- Include availability notes when APIs are new.
## Output format
1. Selected docs (filenames)
2. Plan (3 to 6 bullets)
3. Code (full files or a single cohesive snippet)
4. Why this matches Apple docs (2 to 5 bullets)
5. Pitfalls (short)