axiom audit ux flow

Security Community

Skill notes

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Step 3: Map State-Dependent Views

Read 3-5 key view files to understand: Which views depend on async data loading? Which views have empty/error/loading state handling? Where are the critical user flows? (onboarding, purchase, settings, content creation)

Output

Write a brief Journey Architecture Map (8-12 lines) summarizing: App entry points (main, deep links, widgets, notifications) Navigation structure (tabs, stacks, modals) Critical user flows identified State-dependent views (async data, conditional content)

Phase 2: Detect Known UX Defects

Run all 11 existing detection categories. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map User Journey Architecture

Phase 1: Map User Journey Architecture

02
Step 1: Identify Entry Points

Step 1: Identify Entry Points

03
Step 2: Map Navigation Structure

Step 2: Map Navigation Structure

04
Step 3: Map State-Dependent Views

Read 3-5 key view files to understand: Which views depend on async data loading? Which views have empty/error/loading state handling? Where are the critical user flows? (onboarding, purchase, settings, content creation)

05
Phase 2: Detect Known UX Defects

Run all 11 existing detection categories. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

06
Phase 3: Reason About Journey Completeness

Using the Journey Architecture Map from Phase 1 and your domain knowledge, check for what's *missing* — not just what's wrong with individual screens. Question · What it detects · Why it matters Can users complete every critical flow (onboarding, purchase, content creation) from start to finish without dead ends? · Incomplete critical flows · Users abandon the app at dead ends in core journeys Does every modal presentation have a clear exit path, including when async operations fail mid-flow? · Missing error recovery in modals · Users get stuck in sheets when network calls fail

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Dead-end view · No NavigationPath management · User trapped with no programmatic exit · CRITICAL Gesture-only action · No .accessibilityAction · Flow unreachable for VoiceOver users · CRITICAL Missing loading state · Unhandled async error · User sees blank screen on failure · CRITICAL

08
Phase 5: UX Journey Health Score

Scoring: SMOOTH: No CRITICAL issues, all critical flows complete, >80% state handling coverage, all modals have dismiss paths ROUGH EDGES: No CRITICAL issues, most critical flows complete, some missing states or entry point validation gaps BROKEN JOURNEYS: Any CRITICAL issues (dead ends, dismiss traps), or critical flows incomplete, or <50% state handling

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.