react-doctor/rendering-animate-svg-wrapper

Review Motion-style props on a plain SVG; a wrapper is not a universal SVG performance fix

Validation prompt

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

The detector reports when resolveJsxElementType(...) is exactly 'svg'—normally a plain lowercase <svg>, with limited support for a constant string alias—and any attribute name matches Motion's animation-prop set. It does not resolve <motion.svg>, a motion.create wrapper, or imports, and it does not inspect which SVG property would animate. In normal React, Motion props on a plain <svg> are not evidence of a working Motion animation, and direct SVG animation does not universally force full re-rasterization. Confirm the project actually intended Motion semantics and rule out a custom JSX runtime or another component that consumes these props before changing markup.

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.

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

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

If the plain SVG was intended to be a Motion component, import from the installed Motion package and change only the tag to <motion.svg>, preserving its SVG attributes, children, accessible name, and animation props. Do not add a wrapper by default. A wrapper can be considered only after profiling a whole-object transform or opacity animation and confirming the extra element does not change layout or semantics; it cannot replace path, stroke, fill, filter, or shape animation. If the props belong to another runtime or are intentionally forwarded, keep the code and suppress the heuristic. See https://motion.dev/docs/react-motion-component

Repository-wide copy prompt

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