creating-manager

Creating Manager

Scaffold a complete manager module with protocol-based services and wire it into the dependency system.

Steps

1. Get the manager name from the user (PascalCase, e.g., "Notification", "Payment", "Chat")
2. Read references/templates.md for the 4 file templates + registration snippets
3. Determine which RIB owns this manager (see below)
4. Substitute {ManagerName}, {managerName}, and {RibName} throughout
5. Determine the folder location (see below)
6. Create all 4 files
7. Register in Dependencies.swift and {RibName}Interactor.swift

Determining the RIB

The app may have one or more RIBs (e.g., Core, Onboarding, TabBar). Each RIB has its own Interactor where managers are resolved.

1. Check Root/RIBs/ for existing RIBs — look at the folder names
2. If only one RIB exists (Core), use that
3. If multiple RIBs exist, determine which one needs this manager based on the flow it supports
4. If unclear, ask the user

The {RibName} placeholder defaults to Core — substitute with the actual RIB name.

Folder Location

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.

Registration

Every new manager must be registered in 2 places — see the registration snippets in templates.md.

Dependencies.swift

1. Add let {managerName}Manager: {ManagerName}Manager declaration at the top of init()
2. In the .mock switch arm: create with Mock{ManagerName}Service()
3. In the .dev, .prod arm: create with Prod{ManagerName}Service()
4. After the switch: container.register({ManagerName}Manager.self, service: {managerName}Manager)
5. Follow initialization order — LogManager and AuthManager are created first, all others come after