Audit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout...
Install
npx skills add XiaomiMiMo/MiMo-Code --skill audit -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,007 tokens
- Runs scripts
- No, instructions only
What it does
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Audit
Use this skill when the user wants to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product flow, journey, funnel, onboarding path, checkout path, settings path, screen, or other product experience.
The output is not a loose opinion. The output is:
- Screenshots of the flow
- Those screenshots rendered inline in the report
- A numbered step list
- UX and design findings tied to steps or screenshots
- Accessibility risks tied to steps or screenshots
- Clear limits on what could not be checked from screenshots alone
Critical Overrides
- Refer to the Plugin router $index before proceeding.
- Follow $critical-overrides.
User Context
Before starting, load $user-context and run its preflight script when local shell access is available.
Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant.
Do not inspect every saved reference. Inspect only what the current task needs.
Route
Before auditing:
- Identify the product or surface.
- Identify the flow or task.
- Choose the capture tool.
- Capture the flow.
- Save and inspect each screenshot.
- Return the audit inline with the accepted screenshots.
Output rules:
- Default to a concise inline report with screenshots rendered in the chat.
- Saving screenshots and notes in the workspace is an internal implementation detail. Do not ask the user to choose a local folder.
- If the user explicitly asks for Figma, create the Figma audit board in addition to the inline report.
- After the inline report, ask once:
Want me to plot this out in Figma with the screenshots and notes?
Capture rules:
