tezca-ios-development

Plugin tezca-ios-development from marketplace tezca-ios-marketplace in AchsDCerrillo/tezca_ios_plugin. Commands read from the repo's manifest — 26 days ago.

Skills (12)

• ios-architecture

  Architecture conventions for SwiftUI iOS apps built with the tezca-ios-development skills. Covers the multimodule layout (one local Swift package with Core, Networking, Database, DesignSystem, Navigation, AppFeature and NameFeature targets), the layers (Endpoint/DAO → DataSource → Repository → UseCa

• kmp-bridge

  Connect a Kotlin Multiplatform (KMP) SDK to a SwiftUI iOS app built with tezca-ios-development. Covers wrapping SDK use cases (Kotlin Flows of ResultState through KMP-NativeCoroutines, or SKIE async/AsyncSequence) into Swift use cases that return async values and AsyncThrowingStreams, mapping Kotlin

• make-api

  Create or update API calls in a SwiftUI iOS app (tezca-ios-development) as the remote data source of a feature. It uses Alamofire through the shared APIClient, with an Endpoint enum per feature, Codable DTOs (snake_case JSON, ISO-8601 dates), a a NameRemoteDataSource protocol and implementation, aut

• make-database

  Create or update local storage for a feature in a SwiftUI iOS app (tezca-ios-development). It writes the entity, the DAO and the a NameLocalDataSource with reactive AsyncStream observation, using whichever database the project picked (SwiftData @Model with @ModelActor DAOs, Core Data .xcdatamodeld w

• make-navigation

  Add or change navigation in a SwiftUI iOS app built with tezca-ios-development. Covers typed routes per feature (AppRoute + FeatureRoute), push/pop with NavigationStack through the @Observable Router, sheets and full-screen covers, switching between launch/unauthenticated/authenticated flows (login

• make-repository

  Create or update a repository in a SwiftUI iOS app (tezca-ios-development). It combines the remote (Alamofire) and local (SwiftData, Core Data or GRDB) data sources behind a protocol, offline-first by default (observe the local cache, refresh from the server, write locally first and sync later throu

• make-screen

  Create or update a complete SwiftUI screen in an iOS app (tezca-ios-development) end to end. It writes every layer the screen needs (Alamofire remote data source, local DAO/data source, offline-first or remote-only repository, use cases, @Observable ViewModel) and the UI (Screen + stateless previewa

• make-tests

  Write or update unit tests for a SwiftUI iOS app built with tezca-ios-development, using Swift Testing (@Suite, @Test, #expect) and protocol fakes. Covers remote data sources (FakeAPIClient plus JSON decoding), DAOs and local data sources (in-memory SwiftData, GRDB or Core Data), offline-first repos

• make-usecase

  Create or update a domain use case in a SwiftUI iOS app (tezca-ios-development). Each use case is a Sendable struct with exactly one responsibility and a single callAsFunction. It uses one or more repositories, holds business rules (validation, combining data, permissions, ordering), and returns asy

• make-viewmodel

  Create or update a ViewModel in a SwiftUI iOS app (tezca-ios-development). It is an @MainActor @Observable final class that calls use cases, holds the screen's state (LoadState or form fields) and presentation logic, and exposes intents the screen calls from .task, .refreshable or buttons. There are

• new-feature

  Create a new feature module in a SwiftUI iOS app set up with tezca-ios-development. It adds a NameFeature target and test target to the local Swift package, a route enum in Navigation, a destinations entry point, Factory DI registrations, a String Catalog, and wires it all into AppFeature. Use it wh

• start-ios

  Set up a new or existing SwiftUI iOS app for multimodule MVVM. It creates a local Swift package with Core, Networking (Alamofire), Database (SwiftData, Core Data or GRDB), DesignSystem, Navigation (NavigationStack router) and AppFeature targets, Factory DI, async/await @Observable ViewModels, Local/

Subagents (1)

• ios-architect

  Read-only reviewer for SwiftUI iOS code built with the tezca-ios-development skills. Use it after generating or changing a feature module, before opening a PR, or when the user asks "is this following the architecture?", "review my feature", or "what's wrong with this ViewModel". It checks layering,

Similar plugins