Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
Passed 21 of 22 test cases with the skill, and 18 of 22 without it.
and 2 more in the full report
3 fixed18 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a complete code review of the following Swift and SwiftUI files for my app. Please organize any issues you find by file. For each defect identified, mention the specific file and line numbers, specify the rule that was broken, and give a brief before/after code snippet showing the resolution. Skip any files that don't have issues. Conclude your response with a prioritized summary of the most important fixes to apply first. Here is the code: struct ProfileView: View { @ObservedObject var viewModel: ProfileViewModel var body: some View { Text(viewModel.name) } }
| Checked | Without skill | With skill |
|---|---|---|
| The response formats the issue with bold line reference directly followed by rule description. | Missed | Passed |
| The response does not recommend iOS 14 fallback options or StateObject legacy wrappers. | Missed | Passed |
| The summary section prioritizes findings at the end of the response. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
Review process:
references/api.md.references/views.md.references/data.md.references/navigation.md.references/design.md.references/accessibility.md.references/performance.md.references/swift.md.references/hygiene.md.references/clean-architecture.md.If doing a partial review, load only the relevant reference files.
CRITICAL: Load and apply every applicable reference file (references/*.md) before reporting findings. Rules marked MUST or Never in those files are non-negotiable — flag every violation found, and skip a file only when it has no issues.
Organize findings by file. For each issue:
foregroundStyle() instead of foregroundColor()").Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.