apple-dev

Use this agent when the user requests a code review of Swift or Apple platform (iOS/macOS/watchOS/tvOS) code. Only use when the target files are .swift or the project is an Xcode project. Do NOT use for non-Apple codebases (TypeScript, Python, Rust, Go, etc.). Performs read-only review for quality, correctness, and Apple platform-specific issues. Examples: <example> Context: User completed a feature and wants review of Swift code. user: "Review the changes I just made to NodeDetailView" assistant: "I'll use the apple-reviewer agent to review your changes." </example> <example> Context: User is about to merge a branch in a Swift/iOS project. user: "Review before I merge into main" assistant: "Let me have the apple-reviewer agent examine the changes." </example> <example> Context: User is working on a TypeScript/Node.js project. user: "Review these changes" assistant: DO NOT use apple-reviewer — this is not an Apple platform project. </example>

Performs design quality review (visual hierarchy, color, spacing) of SwiftUI files. Fresh context — evaluates visual quality independently of implementation decisions. Examples: <example> Context: User completed a SwiftUI page and wants visual polish feedback. user: "Review the design of my settings page" assistant: "I'll use the design-reviewer agent to evaluate the visual quality." </example> <example> Context: run-phase completed a phase that created new UI components. user: "Check the visual quality of the new dashboard" assistant: "I'll use the design-reviewer agent for a fresh-context design review." </example>

Performs product + UX completeness review from user journey perspective. Fresh context — validates feature completeness against user scenarios independently. Examples: <example> Context: User completed implementing a feature with full user journey. user: "Review the expense tracking feature for completeness" assistant: "I'll use the feature-reviewer agent to validate the user journey." </example> <example> Context: run-phase completed a phase that delivered a user-facing feature. user: "Check if the onboarding flow covers all scenarios" assistant: "I'll use the feature-reviewer agent for product+UX completeness review." </example>

Performs UI + UX compliance review of SwiftUI files. Use when run-phase completes a phase that modified UI files. Fresh context review — no implementation memory. Examples: <example> Context: User finished modifying several SwiftUI views. user: "Run a UI review on the views I just changed" assistant: "I'll use the ui-reviewer agent to check UI compliance." </example> <example> Context: run-phase completed a phase that modified UI files. user: "Check UI compliance for the updated screens" assistant: "I'll use the ui-reviewer agent for a fresh-context compliance review." </example>

Use when working on Swift, iOS, macOS, iPadOS, SwiftUI, or SwiftData code, editing .swift files, planning Apple platform features, fixing Swift bugs, or reviewing Swift code. Provides essential development rules including build cycle, constraints, concurrency, UI rules, and plan execution principles.

Use when preparing for App Store submission, or the user says 'ASC review', 'prepare submission'. Performs item-by-item App Store Connect submission material check and guidance. Keywords: ASC, App Store Connect, submission, privacy labels, screenshots, review.

Use before refactoring legacy code, or when the user says 'characterization test', 'lock behavior', '特征测试', 'write characterization tests', 'snapshot behavior'. Generates Swift Testing test cases that capture current behavior as a safety net before refactoring.

Use when the user says 'code audit', 'audit code', '代码审计', 'report card', 'security scan', or wants a comprehensive code quality assessment. Scans for security issues, concurrency safety, accessibility gaps, performance anti-patterns, and SwiftUI anti-patterns in iOS/macOS Swift projects.

Use after completing a page/module UI, before visual optimization, or when the user says 'review design' or 'check visual quality'. Reviews visual hierarchy, color strategy, spacing rhythm, and overall polish. Complements /ui-review (code compliance) and /feature-review (user journey).

2 hooks across 2 events