ios-swift-patterns

Data Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: SwiftUI, UIKit, MVVM, Combine, async/await, Core Data, and App Store submission patterns Use when this capability is needed. Pro…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Architecture”, “MVVM + Coordinator Pattern”, “Key Principles”, “SwiftUI Best Practices”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name ios-swift-patterns directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Architecture / MVVM + Coordinator Pattern / Key Principles” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

iOS Swift Patterns

Production-grade iOS development with Swift, SwiftUI, and UIKit.

Architecture

MVVM + Coordinator Pattern

View (SwiftUI/UIViewController)
  ↕ binds to
ViewModel (ObservableObject)
  ↕ calls
Service Layer (Networking, DB)
  ↕
Core Data / API

Key Principles

Views are dumb: They render state and forward actions — no business logic
ViewModels own state: @Published properties, @State only for local UI
Services are stateless: Network calls, DB operations, analytics
Coordinators handle navigation: Removing navigation from views makes them reusable

SwiftUI Best Practices

Performance

Use LazyVStack/LazyHStack for large lists, not VStack
Mark views with @MainActor explicitly
Use equatable() on complex views to prevent unnecessary re-renders
Prefer @State for local, @StateObject for owned, @ObservedObject for passed-in

State Management

// Good: Clear separation
@MainActor
class UserViewModel: ObservableObject {
    @Published var users: [User] = []
    @Published var isLoading = false

    func loadUsers() async {
        isLoading = true
        users = await userService.fetchUsers()
        isLoading = false
    }
}

App Store Submission Checklist

No Hardcoded API keys
TestFlight beta tested with real users
Privacy manifest updated
Screenshots for all required sizes
App Store description and keywords ready
Subscription/IAP products configured

Source: cosmicstack-labs/mercury-agent-skills — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Data
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview ios-swift-patterns.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# iOS Swift Patterns

Production-grade iOS development with Swift, SwiftUI, and UIKit.

## Architecture

### MVVM + Coordinator Pattern
```
View (SwiftUI/UIViewController)
  ↕ binds to
ViewModel (ObservableObject)
  ↕ calls
Service Layer (Networking, DB)
  ↕
Core Data / API
```

### Key Principles
- **Views are dumb**: They render state and forward actions — no business logic
- **ViewModels own state**: `@Published` properties, `@State` only for local UI
- **Services are stateless**: Network calls, DB operations, analytics
- **Coordinators handle navigation**: Removing navigation from views makes them reusable

## SwiftUI Best Practices

### Performance
- Use `LazyVStack`/`LazyHStack` for large lists, not `VStack`
- Mark views with `@MainActor` explicitly
- Use `equatable()` on complex views to prevent unnecessary re-renders
- Prefer `@State` for local, `@StateObject` for owned, `@ObservedObject` for passed-in

### State Management
```swift
// Good: Clear separation
@MainActor
class UserViewModel: ObservableObject {
    @Published var users: [User] = []
    @Published var isLoading = false

    func loadUsers() async {
        isLoading = true
        users = await userService.fetchUsers()
        isLoading = false
    }
}
```

## App Store Submission Checklist
- [ ] No Hardcoded API keys
- [ ] TestFlight beta tested with real users
- [ ] Privacy manifest updated
- [ ] Screenshots for all required sizes
- [ ] App Store description and keywords ready
- [ ] Subscription/IAP products configured

---
> Source: [cosmicstack-labs/mercury-agent-skills](https://github.com/cosmicstack-labs/mercury-agent-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Architecture → MVVM + Coordinator Pattern → Key Principles → SwiftUI Best Practices → Performance → State Management
terms    -> Views are dumb · ViewModels own state · Services are stateless · Coordinators handle navigation
files/cmd -> @Published · @State · LazyVStack · LazyHStack · VStack · @MainActor · equatable() · @StateObject
body sha256 -> 2b228a820709