reviewing-code-changes
Review Swift/SwiftUI code and validate changes. Checks for architecture violations, hardcoded styling, dead code, missed reuse, AppStyle consistency, layout robustness, MVVM compliance, referential integrity, and anti-patterns. Use when the user asks to review code, audit styling, verify architecture, validate changes, or clean up after refactoring.
Repository SourceNeeds Review
create-feature
Scaffold a new SwiftUI feature module, extend an existing feature, or create a picker sheet with correct project conventions. Use when the user asks to create a new feature, screen, page, module, view, tab, picker, calendar, schedule, dashboard, settings, or add functionality to an existing feature. Also use when asked to build a neue Seite, neues Feature, neuer Screen, new screen, or new page in the FitnessApp iOS project.
Repository SourceNeeds Review
debugging-ui-tests
Diagnose and fix failing XCUITest UI tests in the FitnessApp project. Investigate selector-not-found errors, scheme/build-config issues, fixture seeding mismatches after SwiftData refactors, and timing flakes. Use when a UI test fails, when a selector is not found, when investigating timeout errors, or when production-code changes broke UITestLaunchStrategy or test-fixture seeding.
Repository SourceNeeds Review
deep-research
Conduct systematic deep research on technical topics with source verification, triangulation, and citation-backed reports. Use when the user asks for deep research, comprehensive analysis, technology comparison, trend analysis, state of the art review, or architecture evaluation. Not for simple lookups, debugging, or questions answerable with 1-2 searches.
Repository SourceNeeds Review