ios-domain-delivery

Implement scoped SwiftUI and UIKit iOS changes with lifecycle and concurrency checks.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill ios-domain-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-domain-delivery
Source: https://github.com/vTRKA/supervibe/tree/main/skills/ios-domain-delivery
Command: npx skills add https://github.com/vTRKA/supervibe --skill ios-domain-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of iOS feature work turning risky and confusing by enforcing view ownership, concurrency rules, persistence/migration safety, permission correctness, accessibility, and verification/rollback evidence before completion.

Core Features & Use Cases

  • Specialist iOS implementation guidance: Keeps SwiftUI and UIKit changes correctly bounded to the right lifecycle, main-thread ownership, and data boundaries.
  • Concurrency, persistence, and permissions guard rails: Ensures async/await vs Combine ownership is deliberate, privacy keys and denial states are handled, and schema changes include migration and rollback.
  • Evidence-first verification workflow: Drives focused checks, defines failure repair loops, and requires explicit blocker/defer decisions when proof is missing.

Quick Start

Use this skill to implement the smallest iOS SwiftUI or UIKit slice by inspecting the source of truth, making only the owned boundary edits, then validating with the declared scoped command and recording evidence and rollback intent.

Frequently Asked Questions about ios-domain-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement SwiftUI features safely without breaking lifecycle ownership or main-thread boundaries?

Scoped iOS delivery enforces view ownership, main-thread rules, and data boundaries for SwiftUI and UIKit changes, producing PASS, BLOCKED, or DEFERRED outcomes with documented evidence and rollback intent.

What's the best way to handle Swift persistence migration and rollback during feature implementation?

Migration-aware persistence updates require deliberate schema change strategies with explicit rollback planning, ensuring data safety is verified before completion through evidence-first checks and scoped validation commands.

How does structured concurrency in Swift interact with permission-state handling on iOS?

Structured concurrency and permission handling require deliberate async/await versus Combine ownership selection, explicit privacy key configuration, and denial state management before any feature work is marked complete.

Can I use this approach for both UIKit and SwiftUI view-model and service repository work?

Yes, scoped iOS delivery applies to both UIKit and SwiftUI implementation, covering view-model and service/repository boundaries, navigation, and async pipelines while preserving local source-of-truth conventions.

Why do iOS accessibility checks block my feature delivery workflow?

Accessibility verification is a required constraint alongside testing and release constraints, ensuring evidence-first validation occurs before completion and generating explicit blocker or defer decisions when proof is missing.

What are the limitations of scoped iOS delivery for background execution and concurrency changes?

Background execution limits and structured concurrency rules act as guard rails that can BLOCK or DEFER delivery when evidence is missing, preventing risky changes from completing without documented checks and rollback intent.