customer-auditlisted

Universal, multi-agent, VISION-VERIFIED audit that makes any app, website, tool, CLI, API, or MCP server genuinely great. Fans out one agent per surface and exercises EVERY single control (button, field, toggle, menu, tab, swipe, long-press, drag) for real — screenshotting before/after and looking at the result — across every lens: does each control actually work + persist + sync, the "does the UI lie?" trust audit, UI/interaction craft & motion, fresh-eyes customer journeys, competitive teardown, accessibility, performance, security, microcopy, empty/error/edge states. Adversarially verifies every finding, then returns a ranked fix list (or auto-fixes). Detects and uses the available MCP servers (e.g. Playwright for websites) and routes UI findings through the user's installed design skills. Trigger when the user says "audit", "customer audit", "review every page/screen", "find everything wrong or missing", "test every button", "QA this", "make this badass/premium", "is everything working and in sync", or ru
Evil-Bane/argus · ★ 1 · AI & Automation · score 74

Install: claude install-skill Evil-Bane/argus

# /customer-audit — universal, vision-verified, multi-agent audit Reproduce a ruthless, parallel, **ground-truth** audit of ANY target, the way a demanding customer + a senior engineer would together. The method is fixed; the target varies. The whole point is to catch the ONE dead control, the field that doesn't save, the screen that doesn't sync — *before the user trips over it* — and to make the thing feel premium. Default to maximum thoroughness. ## Works on everything `android-app-code` · `running-app` (device/emulator) · `website` · `cli` · `api` · `mcp-server` · `desktop/electron` · `library` · any `code`. Pick the target type, then exercise it the right way. ## Modes (`$ARGUMENTS`) - `/customer-audit` — full audit of the current project (all lenses, all surfaces, every control). - `/customer-audit ui` — craft + motion + a11y + tokens + delight (routed through design skills). - `/customer-audit customer` — fresh-eyes personas + competitive teardown (what's missing/confusing). - `/customer-audit <path|url|surface>` — scope to one area / page / route / command. - `/customer-audit fix` — run, then AUTO-APPLY confirmed fixes (worktree-isolated, verified, committed). - `/customer-audit redesign <surface>` — tournament: generate N design variants, judge, ship the winner. ## The seven steps 1. **Scope.** Identify the TYPE. Infer from the repo/URL; ask ONE short question only if truly ambiguous. 2. **Inventory the environment.** Detect available **MCP servers** (`ToolSearch