SwiftUI Agent Skill is a set of instructions that helps AI coding assistants write and review Apple SwiftUI interfaces, including navigation, layout, state, accessibility, and performance. Developers use it with Claude Code, Codex, Gemini, Cursor, and other supported agents, and the catalogue entry is the skill itself.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add twostraws/SwiftUI-Agent-Skill --skill swiftui-progit clone --depth 1 https://github.com/twostraws/SwiftUI-Agent-SkillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/twostraws/swiftui-agent-skill/swiftui-pro)<a href="https://agentmods.dev/skills/twostraws/swiftui-agent-skill/swiftui-pro"><img src="https://agentmods.dev/badge/skills/twostraws/swiftui-agent-skill/swiftui-pro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/twostraws/swiftui-agent-skill/swiftui-pro"><img src="https://agentmods.dev/badge/skills/twostraws/swiftui-agent-skill/swiftui-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.01278 |
| Opus 5.5 | $0.00014 | $0.00511 |
| Sonnet 5.5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
swiftui-pro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
6 near-identical copies found in the catalogue:
- swiftui-pro — 100% identical, 38 lines differ
- swiftui-pro — 100% identical, 38 lines differ
- swiftui-pro — 100% identical, 2 lines differ
- swiftui-pro — 100% identical, 38 lines differ
- swiftui-best-practices — 97% identical, 49 lines differ
- swiftui-review — 92% identical, 47 lines differ
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Swift and SwiftUI code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems – do not nitpick or invent issues.
Include deprecated API in review findings. During feature work or bug fixes, complete the requested change and suggest unrelated modernization separately; do not apply it without being asked.
Review process:
- Check for deprecated API using
references/api.md. - Check that views, modifiers, and animations have been written optimally using
references/views.md. - Validate that data flow is configured correctly using
references/data.md. - Ensure navigation is updated and performant using
references/navigation.md. - Ensure the code uses designs that are accessible and compliant with Apple's Human Interface Guidelines using
references/design.md. - Review layout behavior as windows resize, including iPad multitasking and folding iPhone Duo, using
references/resizability.md. - Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using
references/accessibility.md. - Check localized text, formatting, and resource handling using
references/localization.md. - Ensure the code is able to run efficiently using
references/performance.md. - Quick validation of Swift code using
references/swift.md. - Final code hygiene check using
references/hygiene.md.
If doing a partial review, load only the relevant reference files.
Keep references/performance-plus.md out of routine reviews. Load it for a requested deep performance review; its more involved changes can also help investigate an established performance problem.
Core Instructions
- iOS 27 exists, and is the default deployment target for new apps.
- Xcode 27.1 and the corresponding 27.1 platform releases are available. Do not dismiss their APIs as speculative.
- iPhone Duo is a folding iPhone, with a small outer display and a large inner display.
- Check the project's deployment target before applying version-specific advice. Use newer runtime APIs only when the target supports them or within an appropriate
#availablecheck. Keep the existing target unchanged. Requirements tied to an Xcode version also need that toolchain; a runtime check cannot make an older SDK recognize a new declaration. - Target Swift 6.4 or later, using modern Swift concurrency.
- As a SwiftUI developer, the user will want to avoid UIKit unless requested.
- Do not introduce third-party frameworks without asking first.
- Break different types up into different Swift files rather than placing multiple structs, classes, or enums into a single file.
- Use a consistent project structure, with folder layout determined by app features.
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 378 B
- agents/openai.yaml 330 B
- assets/swiftui-pro-icon.png 3.0 KB
- assets/swiftui-pro-icon.svg 1.5 KB
- references/accessibility.md 2.6 KB
- references/api.md 11 KB
- references/data.md 6.6 KB
- references/design.md 3.5 KB
- references/hygiene.md 1.4 KB
- references/localization.md 2.3 KB
- references/navigation.md 2.1 KB
- references/performance-plus.md 3.0 KB
- references/performance.md 6.5 KB
- references/resizability.md 11 KB
- references/swift.md 4.7 KB
- references/views.md 6.7 KB
- skills/swiftui-pro/references 16 B
- skills/swiftui-pro/SKILL.md 6.4 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago Changed fc62139e262b
- 16d ago Changed · +14 lines c88c396456cc
- 1mo ago First seen · 109 lines · 36 tokens per session scan A 8b58a171afc1
swiftui-pro is a skill published in the GitHub repository twostraws/SwiftUI-Agent-Skill (6,335 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,278 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
axiom-audit-camera
Use this agent to scan Swift code for camera, video, and audio capture issues including deprecated APIs, missing interruption handlers, threading violations, and permission anti-patterns.
mobile-platform-offline-validate
Review a Lightning Web Component for mobile offline compatibility — the Komaci offline static analyzer that pre-primes the data graph for Salesforce Mobile App Plus and Field Service Mobile App. Produces a finding list with code-level fixes covering inline GraphQL queries in @wire configurations, modern lwc:if /…
mobiai-review-code
Use when reviewing mobile code changes — check for lifecycle issues, memory leaks, thread safety, and platform-specific pitfalls.
review-react-native
Perform a read-only review of React Native and Expo code for cross-platform correctness, lifecycle safety, navigation and deep-link behavior, native configuration, permissions, device storage, list and thread performance, gestures, accessibility, build profiles, and OTA compatibility. Use for pull requests, diffs…