react-doctor/no-tailwind-layout-transition

Review Tailwind transitions of layout properties and preserve real reflow when it is part of the interaction

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

For react-doctor/no-tailwind-layout-transition, the detector reads a literal className. It reports Tailwind transitions that explicitly cover width, height, inset, margin, padding, gap, or size. It cannot prove a positive duration, final computed utility precedence, affected subtree size, or measurable layout cost. Confirm that the named property interpolates. Then determine whether siblings, intrinsic content, clipping, focus geometry, or hit areas must reflow. Use a production trace before describing the finding as user-visible jank. 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 a candidate correction

Apply this candidate correction only after the required evidence confirms the risk.

Reported pattern

const Demo = () => (
  <div className="transition-[margin-top] hover:mt-2">Preview</div>
);

Candidate corrected pattern

const Demo = () => <div className="hover:mt-2">Preview</div>;

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Use the cheapest contract-preserving fix. If only the layout end state matters, remove or narrow the transition. Keep the final margin, size, or spacing state instantaneous. Use translate, scale, opacity, or clip only for a genuinely visual effect whose document flow, text geometry, focus geometry, clipping, and hit area remain equivalent. For real reflow, keep a scoped intrinsic transition or use measured layout projection supported by the installed library. Do not mechanically convert margin or size to transform, and re-profile when performance motivated the change.

Repository-wide copy prompt

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

const Demo = () => (
  <div className="transition-[margin-top] hover:mt-2">Preview</div>
);

const Demo = () => <div className="hover:mt-2">Preview</div>;