Expert in Swift concurrency and networking. Specializes in async/await patterns, actors, URLSession, structured concurrency, and network error handling. Use proactively when implementing API clients, background tasks, concurrent operations, or any networking code.
Core Data / SwiftData specialist. Use proactively when designing data models, adding persistence, optimizing fetch/query performance, debugging data issues, implementing migrations (lightweight/custom), or integrating CloudKit (Core Data + NSPersistentCloudKitContainer). Focus on data modeling, migrations/versioning…
Architecture analyst for planning new features and core changes. Scans project to infer patterns, proposes plan, WAITS for approval. Use for project-wide architecture understanding.
Expert SwiftUI layout specialist for complex layouts, custom view modifiers, geometry calculations, and responsive design. Use proactively when building complex UIs, custom controls, or encountering layout challenges.
Expert testing and quality assurance specialist for XCTest, UI testing, mocking strategies, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
UX/UI design specialist focused on user experience, design system compliance, user flow optimization, and modern iOS design patterns. Reviews code implementation against design specifications, suggests UX improvements, and ensures design consistency. ALWAYS proposes changes and WAITS for user confirmation before…
Annotate Figma UI screens with accessibility annotations — reading order, tab/focus order, Button, Image alt, Role/Value/Label and More info callouts — using the annotation library configured for the project. Use when asked for accessibility annotations, AX annotations, a11y markup in Figma, reading or focus order…
Checks and suggests accessibility improvements for Jetpack Compose and Android Views including TalkBack labels, dynamic text support, and color contrast. Use when creating or modifying UI components, screens, or when the user asks about accessibility.
Use when creating or modifying Flutter UI components, screens, or widgets, or when the user asks about accessibility, screen reader support, VoiceOver, TalkBack, touch targets, color contrast, or WCAG compliance in a Flutter app.
Checks and suggests accessibility improvements for SwiftUI and UIKit code including VoiceOver, Dynamic Type, color contrast, motion, and input methods. Use when creating or modifying UI components, views, or when the user asks about accessibility.
Analyze Jetpack Compose UI hierarchies and suggest MVVM/MVI or other architectural improvements. Use when reviewing existing Compose code, creating new Compose components, analyzing composable structure, or when the user asks about Compose architecture patterns. Best for code review and refactoring guidance.
Review function and class interfaces for Kotlin Coding Conventions compliance. Use when creating public APIs, reusable components, library interfaces, or when the user asks for API design review or Kotlin naming conventions.
Identifies potential performance bottlenecks in Jetpack Compose code including expensive recompositions, unnecessary redraws, and memory issues. Use when code involves lists, animations, complex UI, or when the user asks about performance optimization.
Use when investigating bugs, crashes, or unexpected behavior in a Flutter app. Especially when issues involve Bloc state not emitting, null safety errors, BuildContext after async, GetIt DI failures, method channel mismatches, widget rebuilds, or memory leaks.
Use when reviewing Flutter code for correctness, architecture compliance, design system usage, linting, or testing coverage. Also use before merging a PR or when the user asks for a code review of Dart or Flutter files.
Use when scaffolding a new Flutter feature, setting up the data/domain/view folder structure, creating datasources, DTOs, repositories, or state management classes, or when the user asks how to organize a Flutter project.
Use when assessing feasibility or complexity of a new Flutter feature before implementation. Especially when evaluating API requirements, state management approach, UI component availability, native dependencies, or effort estimation.
Use when implementing a Flutter feature from scratch or completing one in progress. Covers file structure, design system compliance, state management setup, error handling, testing, and buildrunner requirements.
Use when Flutter UI has jank, slow scrolling, excessive rebuilds, or memory leaks. Also use when optimizing lists, animations, or complex widget trees, or when the user asks about Flutter rendering performance.