菜单
Add a new AB test by wiring it through ActiveABTests, all ABTestService implementations, DevSettingsPresenter, DevSettingsView, and CoreInteractor. Use when the user asks to add an AB test, feature flag, remote config test, or experiment. Supports both Bool and enum-based tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | creating-ab-test |
| description | Add a new AB test by wiring it through ActiveABTests, all ABTestService implementations, DevSettingsPresenter, DevSettingsView, and CoreInteractor. Use when the user asks to add an AB test, feature flag, remote config test, or experiment. Supports both Bool and enum-based tests. |
Wire a new AB test through all required files. This is a multi-file mechanical change — every test follows the same pattern across 5+ files.
showBanner, paywallVariant)| Type | When | Example |
|---|---|---|
| Bool | Simple on/off flag | showBanner: Bool |
| Enum | Multiple variants | paywallVariant: PaywallTestOption |
For enum tests, create a {TestName}Option.swift file in Managers/ABTests/Models/ with String, Codable, CaseIterable conformance and a static var default.
| # | File | What to Add |
|---|---|---|
| 1 | Managers/ABTests/Models/ActiveABTests.swift | Property, init param, CodingKey, eventParameters, update method, RemoteConfig init, asNSObjectDictionary |
| 2 | All files in Managers/ABTests/Services/ | Each service conforming to ABTestService must be updated to handle the new test property (see below) |
| 3 | Core/DevSettings/DevSettingsPresenter.swift | State property, loadABTests line, change handler |
| 4 | Core/DevSettings/DevSettingsView.swift | Toggle (Bool) or Picker (enum) in abTestSection |
| 5 | Root/RIBs/Core/CoreInteractor.swift | Computed property exposing the test value |
List all files in Managers/ABTests/Services/ and update every one. The specific services may vary by project (e.g., MockABTestService, LocalABTestService, FirebaseABTestService, MixpanelABTestService, etc.). For each service, read the file and add the new test property following its existing pattern — mock services get an optional init param, local services get a @UserDefault, prod services get a default value.
"_{YYYYMM}_{TestName}" — date-prefixed for easy cleanup of old testsActiveABTestsManagers/ABTests/Services/ and update each one following its existing pattern@UserDefault (Bool) or @UserDefaultEnum (enum) for persistenceTo use the test in a screen:
var {testName}: Bool { get } (or enum type) to the screen's Interactor protocolinteractor.{testName} in the PresenterScaffold a unit test file using the Swift Testing framework. Use when the user asks to create tests, add unit tests, write tests for a manager/presenter/interactor, or scaffold a test file. Mirrors the app's folder structure with _Tests naming convention.
Add a new navigation module to the app. Modules are top-level navigation contexts that replace the entire screen hierarchy (e.g., onboarding, tabbar, admin). Use when the user asks to add a new module, create a new app section that replaces the current flow, or add a new top-level navigation context. Modules use router.showModule and require ModuleWrapperView wrapping.
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.
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.
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.
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.