Add deep link or push notification handling logic to ModuleWrapperPresenter. Use when the user asks to handle a deep link, URL route, universal link, push notification action, or notification tap. Both deep links and push notifications are handled in ModuleWrapperPresenter.swift.

Add a Swift package dependency to the project and wire it in. Use when the user asks to add a package, library, SDK, or third-party dependency. Covers Xcode SPM setup, Alias file creation, logger conformance, and when to use the creating-manager skill for service implementations.

Scaffold a reusable SwiftUI component — pure UI with injected data and actions.

Create a Swift extension file with the Type+EXT.swift naming convention in the Extensions/ folder. Use when the user asks to add an extension, add a helper method to an existing type, or extend a Foundation/SwiftUI/custom type.

Scaffold a new manager with service protocol, Mock/Prod service implementations, register in Dependencies.swift, and resolve in the appropriate RIB's Interactor. Use when the user asks to create a new manager, add a new service, or scaffold a new manager module.

Scaffold a Codable data model with CodingKeys, eventParameters, and mock data. Use when the user asks to create a new model, data type, struct, or enum for the app. Supports both DataSyncModelProtocol models (for database syncing) and simple Codable models.

Scaffold a new paywall variant view in Core/Paywall/Paywalls/ and wire it into the AB test switch. Use when the user asks to add a new paywall, create a paywall variant, add a subscription screen, or build a purchase flow. Covers custom paywalls (most common), StoreKit native paywalls, and RevenueCat paywalls. Every new paywall must be behind an AB test flag.

Scaffold a new VIPER screen module for the iOS app. Creates 4 files (View, Presenter, Interactor, Router) with Builder, Router, Interactor extensions for the correct RIB. Use when the user asks to create a new screen, add a new page, build a new view, or scaffold a new module.

Scaffold a custom SwiftUI ViewModifier in Components/ViewModifiers/. Use when the user asks to create a view modifier, add a reusable modifier, create a custom modifier, or build a View extension that wraps behavior. ViewModifiers encapsulate reusable view transformations (appearance, behavior, layout) and always include a View extension for ergonomic usage.

Rename a VIPER screen across all files including View, Presenter, Interactor, Router, Delegate, CoreBuilder extension, CoreRouter extension, event name strings, and cross-references from other screens. Use when the user asks to rename, refactor, or change the name of a screen.