Verwenden Sie dies beim Erstellen, Ändern oder Überprüfen einer iOS Clean Architecture Präsentationsschicht mit SwiftUI/UIKit Zustandshaltern, explizitem UiState, UiModel-Mapping, Dependency Injection und zustandsbasierter Präsentationscode-Überprüfung.
Dieses Skill hilft Entwicklern, die Präsentationsschicht einer iOS Clean Architecture unter Verwendung von SwiftUI oder UIKit zu erstellen, zu ändern oder zu überprüfen. Es definiert klare Richtlinien für die Verwendung von Zustandshaltern (State Holders) wie ViewModel oder ObservableObject, die den UiState explizit verwalten. Es behandelt auch die Konvertierung von Domänenmodellen in UiModel-Objekte, die für die Benutzeroberfläche optimiert sind. Das Skill fördert die Verwendung von Dependency Injection (entweder manuell oder mit Swinject) und die Implementierung einer zustandsbasierten Präsentationslogik. Es unterstützt die Überprüfung des Codes auf Konsistenz mit Clean Architecture-Prinzipien, einschließlich der Trennung von Belangen und Testbarkeit.
npx skills add https://github.com/chonamdoo/agent-flow/tree/main/skills/ios-clean-presentation-architectureVerwenden Sie dies beim Erstellen, Ändern oder Überprüfen einer iOS Clean Architecture Präsentationsschicht mit SwiftUI/UIKit Zustandshaltern, explizitem UiState, UiModel-Mapping, Dependency Injection und zustandsbasierter Präsentationscode-Überprüfung.
This repo contains 5 individual skills — each has its own dedicated page.
Common code generation and code modification discipline for agent-flow. Use before and during implementation, TDD red/green/refactor, fix-loop, bug fixes, feature work, and any task where Codex, Claude, OMP, or another agent writes or changes code. Enforces start-before, during-implementation, and after-implementation checks without a scoring rubric.
Apply comment-quality criteria during implementation and the final comment-quality pass before final-review, multi-review, or architecture-review after code changes. Applies equally in Codex, Claude, and OMP for Python, Kotlin, React Web, React Native, iOS, Swift, and SwiftUI.
Flutter implementation and review checklist. Use only when writing, modifying, or reviewing Flutter widget code, layout constraints, adaptive sizing, navigation and routing, platform channels, platform views, background entry points, list and image performance, async gaps across `BuildContext`, disposal, theme and design tokens, accessibility, localization, offline and error states, or Flutter test and golden coverage. Do not use for Dart language generalities, native Android or iOS internals beyond the engine and channel-registration seam a Dart entry point depends on, or broad rewrites.
Use when implementing or reviewing iOS app-wide error handling where SwiftUI views/ViewModels notify common errors and an @main App, WindowGroup AppShell, NavigationStack coordinator, or UIKit AppCoordinator owns root navigation, tab/session flow switching, alerts, sheets, toast hosts, SessionExpired handling, Maintenance handling, and root reset behavior.
Synthesizes the current conversation and codebase context into a PRD, then writes or publishes it according to the caller's requested output target. Use when the user asks to turn an already-discussed idea, plan, or conversation into a PRD; use `grilling` first if key decisions are still unresolved.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".