菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scaffold 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.
| name | creating-manager |
| description | 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 complete manager module with protocol-based services and wire it into the dependency system.
{ManagerName}, {managerName}, and {RibName} throughout{RibName}Interactor.swiftThe app may have one or more RIBs (e.g., Core, Onboarding, TabBar). Each RIB has its own Interactor where managers are resolved.
Root/RIBs/ for existing RIBs — look at the folder namesThe {RibName} placeholder defaults to Core — substitute with the actual RIB name.
Managers live in SwiftfulStarterProject/Managers/. Each manager gets its own folder with a Services/ subfolder:
Managers/
{ManagerName}/
{ManagerName}Manager.swift
Services/
{ManagerName}Service.swift
Mock{ManagerName}Service.swift
Prod{ManagerName}Service.swift
Check existing managers in Managers/ for reference.
Every new manager must be registered in 2 places — see the registration snippets in templates.md.
let {managerName}Manager: {ManagerName}Manager declaration at the top of init().mock switch arm: create with Mock{ManagerName}Service().dev, .prod arm: create with Prod{ManagerName}Service()container.register({ManagerName}Manager.self, service: {managerName}Manager)LogManager and AuthManager are created first, all others come afterprivate let {managerName}Manager: {ManagerName}Manager propertyinit(container:): self.{managerName}Manager = container.resolve({ManagerName}Manager.self)!@MainActor @Observable — alwaysLogManager? as optional dependency — alwaysinit — the protocol, not a concrete implementation@MainActor protocol ... : Sendableclass (mutable state for testing) — production service is a struct (unless it needs mutable state)FirebaseAvatarService, RevenueCatPurchaseService). Use Prod{ManagerName}Service only if genericenum Event: LoggableEvent for analytics — event names follow {ManagerName}Man_Action_Status patternDocumentSyncEngine or CollectionSyncEngine composition (see manager-lifecycle rules)Once the skeleton is created, the user will likely want to:
{RibName}Interactor as interactor methodslogIn()/signOut()