Wires Forge apps to backend services by replacing mock managers.
npx skills add https://github.com/sakhnenkoff/forge-ios --skill forge-wire
Please help me install this Agent Skill. Skill: forge-wire Source: https://github.com/sakhnenkoff/forge-ios/tree/main/skills/forge-wire Command: npx skills add https://github.com/sakhnenkoff/forge-ios --skill forge-wire
Connect a Forge app to real backend services. It replaces mock manager implementations with production-ready code that talks to Firebase, Supabase, REST APIs, GraphQL endpoints, CloudKit, or local SwiftData — without touching any View or ViewModel code. The design is backend-agnostic. The developer picks their preferred stack for data, auth, and analytics independently. Each combination is valid. The skill modifies only the manager layer, preserving the MVVM architecture and DS components that forge-app and forge-feature built.
Run /forge:wire to begin connecting your app to production backends.
High-intent search queries and answers about installing and using this skill.
To connect an iOS MVVM app to a real backend without rewriting ViewModels, you replace mock managers with production-ready implementations. This modifies only the manager layer, preserving MVVM architecture and design system tokens while wiring live services.
Yes, you can mix Firebase auth with a REST API data backend in your Swift app. The backend-agnostic configuration lets you independently select data, auth, and analytics options, making every combination valid across Firebase, Supabase, REST, GraphQL, CloudKit, and SwiftData.
You wire a Forge app to live backend services by running the /forge:wire command. This initiates the replacement of mock manager implementations with production-ready code across your selected data, auth, and analytics providers.
Replacing mock managers with production code does not break existing MVVM architecture. The process keeps the manager layer as the only touched component, preserving Views, ViewModels, and design system tokens without requiring structural refactoring.
The best way to configure Dev and Prod environments for an iOS backend integration is through backend-agnostic wiring that modifies only the manager layer. This enables distinct environment setups while keeping the MVVM architecture and design system tokens intact.
Supported backend options for wiring a Swift app to production services include six data backends, four auth options, and five analytics options. Supported data providers cover Firebase, Supabase, REST APIs, GraphQL endpoints, CloudKit, and local SwiftData.
koshkinvvDesign iOS app architectures using MVVM, Clean Architecture, or TCA.
AgentiveCitySet up Supabase integration in Next.js App Router projects with TypeScript.
fumiya-kumeBuild iOS 17+ app guides using SwiftUI and MVVM architecture.
pradeepmouliImplement SwiftData persistence in SwiftUI apps with typed models and declarative queries.
