axiom-audit-ux-flow

Scan SwiftUI and UIKit source code to detect navigation defects and accessibility issues.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-ux-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-audit-ux-flow
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-ux-flow
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-ux-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies critical user journey defects in iOS applications, such as dead-end views, dismiss traps, and missing empty states, which often lead to user frustration and abandonment.

Core Features & Use Cases

  • Automated UX Auditing: Systematically scans SwiftUI and UIKit codebases for navigation anti-patterns and broken user journeys.
  • Defect Detection: Pinpoints specific issues like modal presentations without exit paths, buried primary actions, and unhandled async states.
  • Use Case: Use this tool during a pre-release audit to ensure that your onboarding flow, purchase journey, and deep-link entry points are robust, accessible, and free of navigation dead ends.

Quick Start

Run the axiom-audit-ux-flow skill to perform a comprehensive UX audit on the current iOS project directory.

Frequently Asked Questions about axiom-audit-ux-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit an iOS app for UX navigation defects and dead ends?

To audit iOS app navigation defects, scan SwiftUI and UIKit source code to pinpoint dead-end views, dismiss traps, and missing state handling across critical user journeys. This validates navigation structures and accessibility compliance to ensure a seamless user experience.

What are common navigation anti-patterns in SwiftUI and UIKit source code?

Common navigation anti-patterns include modal presentations without exit paths, buried primary actions, and unhandled async states. These broken user journeys cause dead-end views and dismiss traps that lead to user frustration and abandonment.

How do I detect missing empty states and dismiss traps in an iOS codebase?

Detect missing empty states and dismiss traps by systematically scanning the app architecture in SwiftUI and UIKit code. This automated UX auditing pinpoints broken user journeys, unhandled async states, and modal presentations lacking exit paths.

Can I use an automated UX flow audit for both SwiftUI and UIKit views?

Yes, you can audit both SwiftUI and UIKit views. The scanning process systematically analyzes app architecture across both frameworks to detect navigation anti-patterns, validate accessibility compliance, and resolve critical user journey defects.

When should I run an iOS navigation structure audit before release?

Run an iOS navigation structure audit during pre-release checks to ensure onboarding flows, purchase journeys, and deep-link entry points are robust. This validates that critical user flows are accessible and free of navigation dead ends before deployment.