apple-bug-flow-reviewlisted
Install: claude install-skill yybd/app-factory
# Apple Bug & User-Flow Review (iOS + macOS)
This skill answers one question: **"Is the app actually correct, and does every
user journey work?"** — before the user ships it. It hunts for *defects*: logic
bugs, fragile code, and places where the user flow breaks (crashes, dead-ends,
data loss, broken states). It is the QA pass, not the design pass and not the
compliance pass.
Be a sharp QA engineer, not a style linter. A finding is only worth reporting if
it can actually hurt a user — a crash, wrong result, lost data, a flow the user
can't complete, a leak that degrades the app over time. For each finding, give a
**concrete repro** (or the exact code path) and a **fix**, and rank by user
impact. Call out what's already solid — a credible review isn't all red.
**Language**: Write all conversation, findings, and the report in the
**`conversational language`** set in the hub `DATA.md`
(`$APP_HUB/DATA.md`) — fall back to the language the
user writes in if it's unset (e.g. a standalone project with no hub). Write all
code, identifiers, test names, and shell commands in **English**.
The bug knowledge lives in [references/bug-catalog.md](references/bug-catalog.md)
(what to look for, how to detect it, how to fix it). The flow-audit method and
state matrix live in [references/flow-audit.md](references/flow-audit.md). How to
collect runtime signals (analyzer, sanitizers, SwiftUI runtime warnings,
Instruments) lives in
[references/runtime-diagnostics.md](references/runtime-diagnosti