Flutter audit

Skill musabekisakov-imj/flutter-design-engineer/skills/flutter-audit

Agent skills for product-aware, adaptive, accessible, and visually verified Flutter UI design engineering

Install

npx -y skills add musabekisakov-imj/flutter-design-engineer --skill flutter-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audit existing Flutter interfaces for product hierarchy, visual coherence, interaction quality, adaptive behavior, accessibility, and implementation risks. Use when asked to review, critique, diagnose, assess, or prioritize improvements to Flutter screens or flows; remain read-only unless implementation is explicitly requested.

SKILL.md

2.2 KB, as published. Nobody here has run it

Flutter 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, and references/visual-qa.md for applicable checks. For multi-domain surfaces, also read references/connected-product-workflows.md and 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.