react-doctor/no-long-transition-duration

Review UI transitions longer than one second; duration is primarily a responsiveness and attention concern, not proof of a rendering bottleneck

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.

Confirm the detector parsed a duration above 1000ms from an inline transitionDuration, animationDuration, transition, or animation value. It checks comma-separated segments and their longest duration, skips screen-reader-hidden elements, and excludes recognized infinite animations and one-shot animation shorthands using forwards. A long duration is not itself a performance failure. Suppress deliberate progress/countdown timing, calm ambient motion, explainers, or one-shot brand/onboarding sequences when the duration is essential, the motion can be paused where required, offscreen work is stopped, and reduced motion is handled. Confirm repeated hover, focus, press, menu, tooltip, or other task-critical feedback really waits too long before editing.

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.

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.

Shorten only the interaction whose rendered response feels delayed, preserving its properties, easing, sequencing, and meaning. Useful starting ranges are 100-160ms for press feedback, 125-200ms for tooltips, 150-250ms for menus and dropdowns, and 200-500ms for larger modal or drawer movement. Most repeated micro-interactions should stay below 300ms; larger spatial or explanatory motion can be longer when justified and interruptible. Do not force ambient, progress-linked, or information-carrying animation into a micro-interaction duration. Verify the affected state with normal and reduced-motion settings.

Repository-wide copy prompt

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