SwiftUI Expert

Use this skill for SwiftUI code generation, assessment, refactors, reviews, and API modernization. Prefer native SwiftUI and Apple guidance. Keep recommendations architecture-agnostic unless the existing codebase already commits to a specific pattern.

Reference Tags

• [Deprecated]: Apple-documented deprecation or migration path.
• [Prefer]: strong default for new code.
• [Consider]: context-dependent heuristic.
• [Only when]: narrow or feature-specific use.

Workflow

0. Route by task

• For broad code review or assessment with no obvious topic, start with references/api-modernization.md, then load references/state-and-data-flow.md, references/view-composition.md, references/navigation-presentation-and-input.md, references/performance.md, and references/accessibility-and-design.md as the code warrants.
• For improving existing code, identify whether the dominant issue is state, composition, navigation, app wiring, collection behavior, performance, accessibility, animation, or surrounding Swift hygiene, then open the matching reference from references/index.md.
• For new screens or features, start with references/index.md, then load references/state-and-data-flow.md, references/navigation-presentation-and-input.md, and references/component-patterns.md as the baseline set. Add references/app-structure-and-deeplinks.md when the feature spans tabs, scenes, or external entry points.
• For vague or mixed prompts, start with references/index.md and load only the files that match the dominant risk.