菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
基于 SOC 职业分类
| name | creating-screen |
| description | 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 complete VIPER screen module. Every screen follows the same 4-file pattern with RIBs wiring.
{ScreenName}, {screenName}, and {RibName} throughoutSwiftfulStarterProject/Core/{ScreenName}/The app may have one or more RIBs (e.g., Core, Onboarding, TabBar). Each RIB has its own Router, Interactor, and Builder.
To determine which RIB:
Root/RIBs/ for existing RIBs — look at the folder namesThe {RibName} placeholder defaults to Core — substitute with the actual RIB name (e.g., Onboarding, TabBar).
All 4 files go in Core/{ScreenName}/:
| File | Contains |
|---|---|
{ScreenName}View.swift | Delegate struct, View struct, Preview, {RibName}Builder extension, {RibName}Router extension |
{ScreenName}Presenter.swift | @Observable @MainActor presenter class, Event enum for analytics |
{ScreenName}Router.swift | Protocol extending GlobalRouter, {RibName}Router conformance |
{ScreenName}Interactor.swift | Protocol extending GlobalInteractor, {RibName}Interactor conformance |
{RibName}Builder and {RibName}Router extensions live in the View file, not in the RIB's own filesinteractor and router as private let — typed to the screen's protocols, not the RIB typesonViewAppear calls interactor.trackScreenEvent, all other events call interactor.trackEvent{ScreenName}View_{Action} (e.g., SettingsView_Appear)Once the skeleton is created, build out the screen by:
body{RibName}Interactor extension{RibName}Router already conforms)