SwiftUI Pro
SwiftUI Pro architecture: one entry point, task-specific references
Follow the review order and understand why the deep performance file is optional
What you will learn
- Trace the review path
- Understand the output contract
- Keep deep work conditional
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 references organize guidance by concern.
- The host agent applies the guidance.
- Deep performance rules require an explicit need.
Trace the review path
SKILL.md names checks for modern API, view composition, data flow, navigation, design, resizing, accessibility, localization, performance, Swift and hygiene. Each topic points to a reference file.
This is a retrieval structure for the host agent, not an executable rule engine. The quality of a finding depends on whether the agent opens the relevant reference and relates it to the actual code and OS target.
Understand the output contract
The entry point asks for genuine problems, a severity grouping, locations and suggested changes. It asks the agent not to turn an unrelated modernization idea into an unrequested edit.
A reviewer should distinguish a documented deprecation from a performance suspicion. The latter needs a measurement or a clear source-level cause; a long list of warnings is not a measure of review quality.
Keep deep work conditional
The skill explicitly keeps performance-plus.md out of routine reviews. That file covers more involved data and view restructuring for a requested deep performance review or a demonstrated problem.
Selective loading saves context and avoids complex refactors on a casual pass. It also means a general review may not cover every advanced performance technique. State the requested scope when comparing results.
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
Read SKILL.md to see the review sequence.
- 2
Open only the references relevant to the question.
- 3
Separate ordinary findings from deep restructuring.
Copy-ready example
SKILL.md
-> api, views, data, navigation
-> accessibility, resizability, performance
-> performance-plus only for a deep requestFrequently asked questions
Does the skill execute static analysis?
The inspected files are instructions and Markdown references; they do not replace a compiler or analyzer.
Why omit performance-plus.md in a normal review?
The entry point reserves it for a deep request or established performance problem.
Sources
- SwiftUI Pro / swiftui-pro/SKILL.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/performance.mdSource checked 2026-10-14
- SwiftUI Pro / swiftui-pro/references/performance-plus.mdSource checked 2026-10-14