From SwiftUI
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.
How this command is triggered — by the user, by Claude, or both
Slash command
/swiftui:SKILLswiftui-review/The summary Claude sees in its command listing — used to decide when to auto-load this command
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: 1. Check for deprecated API using `references/api.md`. 1. Check that views, modifiers, and animations have been written optimally using `references/views.md`. 1. Validate that data flow is configured correctly using `references/data.md`. 1. Ensure navigation is updated and performant using `references/navigation.md`. 1. Ensure the code uses designs that are accessible and compliant with Apple’s Human Interfac...
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.
Example output:
Line 12: Use foregroundStyle() instead of foregroundColor().
// Before
Text("Hello").foregroundColor(.red)
// After
Text("Hello").foregroundStyle(.red)
Line 24: Icon-only button is bad for VoiceOver - add a text label.
// Before
Button(action: addUser) {
Image(systemName: "plus")
}
// After
Button("Add User", systemImage: "plus", action: addUser)
Line 31: Avoid Binding(get:set:) in view body - use @State with onChange() instead.
// Before
TextField("Username", text: Binding(
get: { model.username },
set: { model.username = $0; model.save() }
))
// After
TextField("Username", text: $model.username)
.onChange(of: model.username) {
model.save()
}
foregroundColor() on line 12 should be foregroundStyle().End of example.
references/accessibility.md - Dynamic Type, VoiceOver, Reduce Motion, and other accessibility requirements.references/api.md - updating code for modern API, and the deprecated code it replaces.references/clean-architecture.md - Clean Architecture patterns, layer separation, MVVM, dependency injection, and modern SwiftUI architecture.references/design.md - guidance for building accessible apps that meet Apple’s Human Interface Guidelines.references/hygiene.md - making code compile cleanly and be maintainable in the long term.references/navigation.md - navigation using NavigationStack/NavigationSplitView, plus alerts, confirmation dialogs, and sheets.references/performance.md - optimizing SwiftUI code for maximum performance.references/data.md - data flow, shared state, and property wrappers.references/swift.md - tips on writing modern Swift code, including using Swift Concurrency effectively.references/views.md - view structure, composition, and animation.npx claudepluginhub daisycatts/dotclaude --plugin swiftui/SKILLEnables work verification for a task. Claude completes the work, verifies it, and appends a verified tag before session exit.
/SKILLResolves a GitHub issue by creating an isolated worktree, implementing a TDD fix, and opening a PR with auto-closing keywords.
/SKILLSurfaces the current session task from a state file and evaluates its clarity and completeness. Reports completion status or identifies remaining steps.