SwiftUI Pro

Pick a task and get started

Install and confirm that the Skill and references are readable, then try the first task with its supplied input. The other tasks use real project material and define what will be delivered and verified.

1. Install SwiftUI Pro in the target project

   Copy install command

   Run the author’s command from the target project, selecting your assistant and project scope. Confirm swiftui-pro and its references are readable afterward. Claude plugins are an alternative documented in the README; adding a marketplace and installing the plugin are separate steps.

   npx skills add https://github.com/twostraws/swiftui-agent-skill --skill swiftui-pro

   Read the author’s setup guide

   Confirm the entry point, then try the static review

   After installation, check that swiftui-pro is available in your configured assistant. The author documents /swiftui-pro in Claude Code, $swiftui-pro in Codex, and invocation by name in natural language. The first task’s iOS 17 / Xcode 27.1 context is hypothetical and needs no new app. For real code, use actual project settings and SDK declarations.

   Read the author’s installation and invocation instructions

2. Give your AI this first task

   Copy prompt

   Prompts, exercise excerpts, and report filenames are editorial conventions. We did not install the Skill, compile SwiftUI, or run measurements. The listed artifacts are task requirements.

   Use swiftui-pro for a focused static review. Confirm that swiftui-pro’s SKILL.md and api.md, data.md, and accessibility.md in its references directory are readable. Do not load performance-plus.md. This ProfileView.swift excerpt is an editorial exercise, not a live project. Assume Xcode 27.1 / Swift 6.4 with an iOS 17 deployment target. ProfileModel is a bindable @MainActor @Observable class with a String username and save() and addContact() methods. addContact creates a contact. The requirement is to call save for every write through the text-field binding, including an equal-value write, but not for a direct programmatic assignment to username. struct ProfileView: View { @Bindable var model: ProfileModel var body: some View { VStack { Text("Profile").foregroundColor(.blue) TextField("Username", text: Binding( get: { model.username }, set: { model.username = $0; model.save() } )) Button(action: model.addContact) { Image(systemName: "plus") } } } } Write swiftui-review.md, grouping findings by excerpt line, rule, actual consequence, and a short before/after change, followed by impact priority. Report supported problems only. Inspect the text color API, the icon button’s action name, and the binding setter’s side effect. A preference for projected bindings is not a reason to move save into onChange mechanically. Also provide binding-checks.md comparing a new value written through the binding, the same value written through it, and a new value assigned directly by code. Explain that onChange observes value changes rather than every binding write. Retain the custom binding if a replacement would change the requirement. Check Apple’s API declarations against the iOS 17 target. If the SDK cannot be inspected, state that limitation; do not raise the target. Produce review documents only. Label conclusions as static reasoning and compilation, VoiceOver, and event-count tests as not run.

3. Check what you receive

   • swiftui-review.md identifies excerpt lines, consequences, and candidate code. The icon button needs a name conveying “Add Contact,” not merely the shape of its symbol.
   • binding-checks.md compares three write paths. Preserve the specified saving behavior rather than treating a projected binding with onChange as an equivalent replacement in every case.
   • Findings remain static reasoning. A real project still needs compilation, actual VoiceOver output, and side-effect counts checked.
   Read the author’s notes for this task