New
Introducing React Bench, see how different models perform on React code

react-doctor/no-excessive-motion-stagger

Review stagger spacing above 80ms in the context of item count, total tail, frequency, and product intent

Status
Active
Category
Design
Assessment
Creative-direction review
Required evidence
source code, rendered UI, product intent
Default configuration
Disabled until configured
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
react
Requirements
react
Tags
design, test-noise
Priority
Unranked; sorts as P3
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Creative-direction review: This rule is explicitly classified as a preference. Review it against the product brief, rendered context, brand system, and user needs. Keeping an intentional choice with evidence is a successful outcome.

Validation prompt

Review the reported pattern in context before deciding whether an edit is warranted.

For react-doctor/no-excessive-motion-stagger, the detector inspects resolved Motion transition objects. It reports staggerChildren above 0.08 seconds or delayChildren: stagger(<literal>) above 0.08 when stagger comes from framer-motion or motion/react. It does not know the rendered child count, total tail, first-item timing, content availability, or replay frequency. Suppress a rare narrative group when its delay is bounded, interaction remains available, order is meaningful, and reduced motion is handled. Judge the rendered sequence rather than treating 80ms as a universal threshold. The Before example is representative, not exhaustive.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

The design tag controls activation and discovery. It does not determine the rule’s proof class.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Review the pattern

This revision is illustrative, not proof that the reported pattern is wrong. Keep intentional choices that fit the product brief and design system.

Reported pattern

import { motion } from "motion/react";

const Demo = () => (
  <motion.ul transition={{ staggerChildren: 0.2 }}>
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
  </motion.ul>
);

One possible revision

import { motion } from "motion/react";

const Demo = () => (
  <motion.ul transition={{ staggerChildren: 0.05 }}>
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
  </motion.ul>
);

Fix prompt

Treat this as review guidance, not a required correction. Preserve an intentional choice when the brief, design system, and rendered evidence support it.

Adjust stagger only when the rendered tail materially delays content or repeatedly disrupts the interaction. Reuse the project's choreography token when available. Otherwise reduce the interval, item count, or staggered subset until the total tail fits the interaction. Preserve item order, the first-item timing, transition type, interruption, and reduced-motion behavior. Do not force every sequence to 50ms or remove an intentional rare narrative sequence only to silence the heuristic.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Review every confirmed react-doctor/no-excessive-motion-stagger diagnostic in the current repository.

Revise only when evidence supports the candidate adjustment.

  • Adjust stagger only when the rendered tail materially delays content or repeatedly disrupts the interaction. Reuse the project's choreography token when available. Otherwise reduce the interval, item count, or staggered subset until the total tail fits the interaction. Preserve item order, the first-item timing, transition type, interruption, and reduced-motion behavior. Do not force every sequence to 50ms or remove an intentional rare narrative sequence only to silence the heuristic.

Validation before editing:

For react-doctor/no-excessive-motion-stagger, the detector inspects resolved Motion transition objects. It reports staggerChildren above 0.08 seconds or delayChildren: stagger(<literal>) above 0.08 when stagger comes from framer-motion or motion/react. It does not know the rendered child count, total tail, first-item timing, content availability, or replay frequency. Suppress a rare narrative group when its delay is bounded, interaction remains available, order is meaningful, and reduced motion is handled. Judge the rendered sequence rather than treating 80ms as a universal threshold. The Before example is representative, not exhaustive.

Reference transformation:

Before

import { motion } from "motion/react";

const Demo = () => (
  <motion.ul transition={{ staggerChildren: 0.2 }}>
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
  </motion.ul>
);

After

import { motion } from "motion/react";

const Demo = () => (
  <motion.ul transition={{ staggerChildren: 0.05 }}>
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
    <motion.li />
  </motion.ul>
);

Constraints:

  • Treat the Before example as representative. Confirm the detector conditions, not an exact text match.
  • If revising, make the smallest change that addresses the observed tradeoff.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • This rule is explicitly classified as creative-direction review. The design tag alone never determines proof class.
  • Inspect the product brief, rendered context, and existing design system before editing.
  • Keep an intentional pattern that is consistent with the project, and report why it stays.
  • Verify accessibility and performance claims with rendered or runtime evidence.
  • Use existing brand assets, product facts, content, and design tokens.
  • Do not invent claims, customer data, typefaces, artwork, or a new visual direction.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not change code only to silence this heuristic.
  • Confirm this rule is enabled for the project: react.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Re-read the changed code and inspect the affected rendered state at relevant viewport, theme, input, and motion settings.
  • If rendered verification is unavailable, report that limitation instead of claiming the design is fixed.
  • If revised, rerun React Doctor and report whether the diagnostic remains. If kept, cite the brief, design-system, or rendered evidence.
  • Report the files changed and any checks you could not run.