swiftui-skills — Claude Code skill: SwiftUI and setup
This skill gives an agent Xcode-bundled Apple guidance for writing and reviewing SwiftUI. Use it when you want code grounded in those docs.
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a claude-codeWhat swiftui-skills does
The package combines Apple documentation shipped with Xcode and instructions for the agent. For coding tasks, the agent selects relevant files, outlines a plan, and produces Swift code. For reviews, it reports issues and improvements with references to the material it consulted. Its response is organized around selected docs, code, and brief notes on pitfalls.
Claims and APIs must be backed by files in /docs. If that folder has no Markdown documentation, run setup.sh from the installed skill directory before asking for SwiftUI guidance. The skill also requires xcodebuild. It tells the agent not to invent APIs and to note availability requirements for newer ones.
What it helps with
- write SwiftUI code grounded in Apple documentation
- review a SwiftUI implementation and list issues
- locate relevant guidance in Xcode docs
- flag availability requirements for newer APIs
Example prompts for the agent
- Build this settings screen in SwiftUI using the Apple docs.
- Review this SwiftUI code and cite the docs behind each finding.
- Rewrite this view using idiomatic SwiftUI and note API availability requirements.
How to install swiftui-skills
1Skills CLI (Vercel)
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a claude-code2Manually: put the files in place
~/.claude/skills/swiftui-skills/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/swiftui-skills/
1Skills CLI (Vercel)
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a codex2Manually: put the files in place
.agents/skills/swiftui-skills/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a cursor2Manually: put the files in place
.cursor/skills/swiftui-skills/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ameyalambat128/swiftui-skills swiftui-skills2Manually: put the files in place
.github/skills/swiftui-skills/SKILL.md1Skills CLI (Vercel)
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a gemini-cli2Platform CLI
gemini skills install https://github.com/ameyalambat128/swiftui-skills --path skills/swiftui-skillsManually: put the files in place
.devin/skills/swiftui-skills/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about swiftui-skills
How do I install swiftui-skills in Claude Code?
Run npx skills add ameyalambat128/swiftui-skills --skill swiftui-skills -a claude-code. The skill file is at ~/.claude/skills/swiftui-skills/SKILL.md.
What does swiftui-skills do?
It guides an agent to use Apple documentation from Xcode when writing or reviewing SwiftUI. API claims should be supported by files in /docs.
What does swiftui-skills need to work?
The /docs folder needs Markdown files extracted from Xcode documentation; setup.sh handles setup. The skill also requires xcodebuild.
Source text
SKILL.md · MIT
---
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)
© ameyalambat128 · MIT · ameyalambat128/swiftui-skills
