About flutter-audit
Flutter UI Audit is a read-only skill for diagnosing Flutter interface issues before suggesting changes. It inspects implementation and rendered states, prioritizes findings by impact, and distinguishes observed facts from visual judgment.
Key features
- 01Inspect screens, state, navigation, and tests
- 02Evaluate accessibility and responsive layouts
- 03Check loading, error, and other UI states
- 04Prioritize findings by impact
- 05Cite evidence and recommend remedies
Use cases
- 01Audit a Flutter screen before redesign
- 02Assess accessibility and adaptive behavior
- 03Identify gaps in UI states and recovery paths
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/flutter-auditin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/anti-slop.mdconnected-product-workflows.mdlayout-and-density.mdvisual-qa.mdDetails
From the project READMEFlutter UI Audit
Diagnose before prescribing. Keep audit work read-only unless the user requests changes.
Inspect
- Read the screen, related state, navigation, theme, shared widgets, and tests.
- Run the app or inspect screenshots when available. Record viewport, theme, locale, and state for each observation.
- Evaluate:
- product goal and primary action;
- hierarchy, grouping, scan order, density, typography, color, and surface use;
- navigation, forms, feedback, destructive actions, and recovery;
- loading, empty, partial, error, offline, and success states;
- compact and expanded layouts;
- semantics, focus, text scaling, contrast, touch targets, RTL, and reduced motion;
- widget boundaries, hard-coded dimensions, rebuild scope, and theme consistency.
- Read
references/anti-slop.md,references/layout-and-density.md, andreferences/visual-qa.mdfor applicable checks. For multi-domain surfaces, also readreferences/connected-product-workflows.mdand verify that the connection is more than adjacent cards.
Prioritize
Classify findings:
- P0: blocks a core task, creates data loss/security risk, or makes the interface unusable.
- P1: materially harms comprehension, accessibility, completion, or adaptive behavior.
- P2: weakens consistency, polish, or maintainability without blocking the task.
- P3: optional refinement with limited user impact.
For each actionable finding, cite the screen/state and relevant file or rendered evidence. Explain user impact and the smallest credible remedy. Separate facts from visual judgment.
Deliver
Lead with the highest-impact pattern, not a long checklist. Include strengths that should be preserved, prioritized findings, missing evidence, and a recommended sequence. Do not imply verification for states you did not render or inspect.