# workflow-audit

     

**A 5-layer audit of SwiftUI user flows. Enumerates entry points, traces critical paths, detects 32 categories of workflow bug, evaluates UX impact, and verifies data wiring.**

**This checks behavior, not code style.** Most code checkers read your app one file at a time and compare it against a list of rules — is this line written correctly? workflow-audit asks a different question: *can a person actually get from here to there and finish what they came to do?*

So it walks your app the way a user would. It starts at every door into a feature — a button, a menu item, a card on the dashboard — and follows each one forward: this button opens that screen, that screen has these three actions, this action leads somewhere else. Then it asks at each step what a real person would ask. Can I get to this screen at all? Now that I'm here, is the button I need visible without scrolling? I finished the task — did anything tell me it worked? I changed my mind — can I get back out?

That's why it finds a kind of bug a file-by-file checker structurally cannot. Consider a screen you built that no button anywhere opens. Every line of that screen is correct. It compiles, it would look fine in review, and no rule is broken — the only thing wrong is that the path to it was never connected, and the shipped app quietly doesn't include the feature. The same goes for a value your app carefully calculates and a screen that carefully displays it, when the two were never wired to each other: both files p