SwiftUI workflow audit — find dead ends, broken promises, and UX friction
npx claudepluginhub terryc21/workflow-auditSwiftUI workflow audit — find dead ends, broken promises, and UX friction. Bundled with a phased plan generator.
Terryc21Built for Stuffolio, an iOS/macOS inventory management app.
A Claude Code plugin that audits SwiftUI user workflows for dead ends, broken promises, and UX friction.
claude plugin marketplace add Terryc21/workflow-audit
claude plugin install workflow-audit
| Skill | Command | Description |
|---|---|---|
| Workflow Audit | /workflow-audit | 5-layer UI audit: discover entry points, trace flows, detect issues, evaluate UX, verify data wiring |
| Plan | /plan --workflow-audit | Consume audit findings into a phased fix plan with per-task prompting |
| Rating System | (shared reference) | Standardized rating format used by both skills |
/workflow-audit for a full 5-layer audit/plan --workflow-audit to generate a phased fix planThe SKILL.md is the methodology in markdown. You can paste it as context in any AI tool that has file access (Cursor, Windsurf, Copilot Chat, etc.) and get most of the value.
Starter prompt for other AI tools:
You are a code auditor for iOS/SwiftUI projects. I'm giving you a skill
document that describes a multi-phase UI workflow audit.
1. Read the methodology sections — they define HOW to scan
2. Follow the phase order: Discovery → Flow Tracing → Issue Detection →
Semantic Evaluation → Data Wiring
3. For each phase, enumerate candidates FIRST, then verify each one —
do NOT just search for known anti-patterns
Key principle: orphaned views and unwired data have no code signature
to search for. You find them by listing everything that SHOULD be
connected, then checking which ones aren't.
Here is the skill document:
[paste SKILL.md contents]
Start with Phase 1: list all view files and their navigation connections.
What Claude Code adds: Automated tool integration (Grep, Glob, Bash), multi-phase session management, finding lifecycle tracking, and cross-skill handoffs. The prompt approach gets you the scanning methodology; Claude Code automates the execution.
Run individual layers when you don't need a full audit:
| Command | What it does |
|---|---|
/workflow-audit layer1 | Discovery — find all UI entry points |
/workflow-audit layer2 | Trace — follow critical user paths |
/workflow-audit layer3 | Issues — detect dead ends, buried buttons, dismiss traps, and more |
/workflow-audit layer4 | Evaluate — assess user impact |
/workflow-audit layer5 | Data wiring — verify real data usage |
/workflow-audit trace "A → B → C" | Trace a specific user flow path |
/workflow-audit diff | Compare current findings against previous audit |
/workflow-audit fix | Generate fixes for found issues |
/workflow-audit status | Show audit progress |
The workflow audit uses a 5-layer approach:
Findings are rated using a standardized table format with Urgency, Risk, ROI, Blast Radius, and Fix Effort columns. Tables adapt to terminal width — narrow terminals get a compact view with the full table in the report file.
For how Workflow Audit differs from pattern-based tools (linters, compiler warnings, code review), and how it pairs with Bug Prospector, see How It Works.
Want all 22 Xcode development skills (testing, debugging, refactoring, release prep, security audit, and more)?
claude plugin marketplace add Terryc21/xcode-workflow-skills
claude plugin install xcode-workflow-skills
Plugins like workflow-audit are tools, not oracles.
Development marketplace for Superpowers core skills library
Harness-native ECC skills, hooks, rules, MCP conventions, and operator workflows
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.