/swiftui-skills
Apple-authored SwiftUI and platform guidance extracted from Xcode. Helps AI agents write idiomatic, Apple-native SwiftUI with reduced hallucinations.
$ npx -y skills add ameyalambat128/swiftui-skills --skill swiftui-skills --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/swiftui-skills
Context preview
The summary Claude sees to decide when to auto-load this skill.
Apple-authored SwiftUI and platform guidance extracted from Xcode. Helps AI agents write idiomatic, Apple-native SwiftUI with reduced hallucinations.
SKILL.md
swiftui-skills.SKILL.mdname: 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)
Read more
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)
Apple-authored SwiftUI and Apple platform guidance, packaged as skills for AI coding agents.