菜单
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.
用 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-model |
| description | 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 data model with the correct conformances, CodingKeys, analytics parameters, and mock data.
{ModelName}, {modelName}, and {modelname} throughout| Type | When to Use | Conformances |
|---|---|---|
| Data Sync Model | Model will be synced to/from a database via DataManagers | DataSyncModelProtocol (StringIdentifiable, Codable, Sendable) |
| Simple Model | Local config, UI state, or API response that isn't database-synced | StringIdentifiable, Codable, Hashable |
| Enum Model | Fixed set of options (AB test variants, categories, status) | String, Codable, CaseIterable |
If unclear, ask the user whether the model will be synced to a database.
Models live under their related manager: Managers/{ManagerName}/Models/
Managers/ to determine which manager owns this model{ModelName}Model.swift / {ModelName}Model — enum models omit the Model suffixpublic struct with public var id: String — required by DataSyncModelProtocolcase firstName = "first_name")eventParameters — computed property mapping each property to a prefixed analytics key using CodingKeys raw values. Prefix with the model's lowercase name, max 8 characters (e.g., "user_\(CodingKeys.email.rawValue)"). Check existing models in Managers/**/Models/ to ensure no other model uses the same prefix — if there's a conflict, abbreviate (e.g., "avatar" → "avtr", "message" → "msg")static var mock returns mocks[0] — static var mocks returns an array of realistic test instances?) unless truly required — models from a database may have missing fieldsinit with all properties as parameters — use default values of nil for optionalsimport SwiftfulDataManagers only for data sync models — simple models just need import SwiftUI