SwiftUI Pro
Read the SwiftUI Pro source: API, state and view rules
Navigate the actual Markdown files before trusting a generated code change
What you will learn
- Start with declared entry points
- Compare rules with code
- Trace navigation and access
Before you start
- A disposable SwiftUI screen
- A supported coding-agent host
- A known deployment target
Use a small screen to decide whether the skill earns a place in your workflow
Key takeaways
- The rule files are the meaningful source code here.
- Soft deprecations need deliberate checking.
- Compilation does not prove accessible behavior.
Start with declared entry points
README.md describes installation and invocation; .claude-plugin/marketplace.json points at swiftui-pro. SKILL.md contains the review order and output instructions.
There is no hidden TypeScript or Swift implementation behind these paths in the inspected package. The source to review is primarily the wording of the rule and the examples in its reference file.
Compare rules with code
The API reference discusses soft deprecations that may not trigger an Xcode warning. The data reference addresses state ownership and property wrappers; the views reference addresses composition and modifiers.
For a suggested replacement, inspect the specific example and the app target. A rule that is right for a new iOS project may need a guarded fallback in an app supporting older versions.
Trace navigation and access
The navigation reference favors NavigationStack or NavigationSplitView over NavigationView. The accessibility reference discusses Dynamic Type, VoiceOver and reduced motion.
A generated patch can compile and still harm navigation or accessibility. Check the changed flow with assistive settings even after a green build. The series did not execute these examples.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Open the entry point and identify the cited reference.
- 2
Match the cited rule to the exact SwiftUI code.
- 3
Build and test the resulting behavior.
Copy-ready example
README.md -> installation
marketplace.json -> swiftui-pro
SKILL.md -> references/api.md + data.md + views.mdFrequently asked questions
Where is the plugin entry?
The pinned marketplace manifest names swiftui-pro and points to its directory.
Does a soft deprecation always warn in Xcode?
The pinned API reference says some older declarations use a soft deprecation marker and remain silent.
Sources
- SwiftUI Pro / README.mdSource checked 2026-10-14
- SwiftUI Pro / .claude-plugin/marketplace.jsonSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/SKILL.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/api.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/data.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/views.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/navigation.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/accessibility.mdSource checked 2026-10-14