Quality check and Audit
Every version gets a quality score, and the Audit tests smoothness like a test runner.
EaseKit checks every animation it renders. The AI sees the findings after each render and fixes blockers and warnings before it answers, and you can read them too. The Quality tab reviews the design; the Audit tab tests the motion frame by frame.
Quality
The Quality tab shows a score from 0 to 100 with a grade: Excellent (90+), Good (75–89), Needs work (60–74) or Critical (below 60). Blockers cost 25 points, warnings 8 and notes 2. Six questions show what passes:
| Dimension | Question | Looks at |
|---|---|---|
| Clarity | Are transitions easy to follow? | Stagger, overload, teleporting, exit paths, crossfades |
| Consistency | Is the motion consistent? | Curve families, durations, directions |
| Readability | Is text readable for long enough? | About 0.5 s plus 0.3 s per word, type size, WCAG contrast |
| Start & end | Are the start and end deliberate? | Idle start, the hook, first frame, end hold, loop seam |
| Craft | Are timing, curves and physics right? | Durations for the context, ease-in on entrances, bounce, scale from 0, overshoot, exits vs entrances, linear motion |
| Style fidelity | Does the animation stay in the session style? | How closely the session style is matched |
Findings is folded to one line with counts per severity; it opens by itself while something blocks. Each finding has a suggestion (→ …). Click one to select its layer and jump to its moment.
Audit
The Audit tab replays the animation like a test runner (“Checking 3/7…”) and gives each case a badge: Pass, Check, Fail or Perf (in German: OK, Prüfen, Fehler, Leistung). A passing case shows only what matters, so a clean jump check doesn't add a separate metric:
| Case | What it checks |
|---|---|
| Speed transitions | A movement that continues across keyframes mustn't change speed abruptly at the joins |
| No jumps | Visible elements mustn't change position or size within a single frame (except deliberate holds) |
| Soft starts | Anything visible and at rest should accelerate instead of snapping into motion |
| Per-frame speed | More than about 48 pt per frame at 60 fps strobes |
| Curve consistency | Movements of the same kind share one curve family |
| Performance (Web) | Only transform and opacity are guaranteed to run on the GPU |
| Reduced Motion | With Reduce Motion on, the end state stays the same |
- Open the Audit tab.
- Read the findings. Each names the layer (
@id) and the time. - Under Debug, turn on Boxes and Paths to see bounding boxes and motion trails on the stage. Dot spacing equals speed.
- Click Fix with AI to send the findings to the chat, or fix them by hand. Click the refresh button to check again.