Usado ao implementar ou revisar o tratamento de erros em todo o aplicativo iOS, onde views/ViewModels do SwiftUI notificam erros comuns e um App @main, WindowGroup AppShell, coordenador NavigationStack ou AppCoordinator UIKit gerencia navegação raiz, alternância de fluxo de abas/sessões, alertas, sheets, hosts de toast, tratamento de SessionExpired, tratamento de Maintenance e comportamento de reset raiz.
Esta skill é projetada para auxiliar desenvolvedores iOS na implementação ou revisão de um sistema abrangente de tratamento de erros em aplicativos, abrangendo desde a camada de visualização até o gerenciamento de navegação raiz. Ela define como views e ViewModels do SwiftUI podem notificar erros comuns, como erros de rede ou de lógica de negócio, e como esses erros são tratados centralizadamente por um shell de aplicativo (AppShell) ou um coordenador de aplicativo (AppCoordinator) no UIKit. A skill suporta múltiplas arquiteturas, incluindo SwiftUI com NavigationStack, UIKit com coordenadores, e sistemas de abas/sessões, garantindo que ações como exibir alertas, sheets, toasts, manipular expiração de sessão (SessionExpired), manutenção (Maintenance) e reset da navegação raiz sejam tratadas de forma consistente. Baseada em uma documentação detalhada (SKILL.md), ela fornece diretrizes para que agentes de IA, como Claude Code, possam gerar ou revisar código que implemente esse padrão de forma robusta e escalável.
npx skills add https://github.com/chonamdoo/agent-flow/tree/main/skills/ios-app-shell-error-handlingUse ao implementar ou revisar o tratamento de erros em todo o aplicativo iOS, onde views/ViewModels do SwiftUI notificam erros comuns e um App @main, WindowGroup AppShell, coordenador NavigationStack ou AppCoordinator UIKit gerencia navegação raiz, alternância de fluxo de abas/sessões, alertas, sheets, hosts de toast, tratamento de SessionExpired, tratamento de Maintenance e comportamento de reset raiz.
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 creating, modifying, or reviewing an iOS Clean Architecture presentation layer with SwiftUI/UIKit state holders, explicit UiState, UiModel mapping, dependency injection, and state-based presentation code review.
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".