react-doctor/style-prop-object

Pass the `style` prop as an object literal like `{{ color: 'red' }}`, never a string or other primitive.

Validation prompt

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

Fires when a style prop resolves to a non-object: a string/number/boolean/regex literal, a template literal, an identifier whose initializer is one of those, or a no-initializer binding whose TS type is a primitive (including a union like string | undefined). In JSX this only checks intrinsic lowercase HTML/SVG tags: custom (capitalized) components in JSX, plus any name in the allow list, are left alone. But the React.createElement(...) path checks the style key regardless of capitalization, so React.createElement('div', { style: 'x' }) AND React.createElement(MyComp, { style: 'x' }) both fire unless MyComp is allow-listed; object literals, null/undefined, member access (props.styles), Object.assign(...), imports, spread props, and any unresolvable expression are always left alone.

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.

Pass style as an object whose keys are camelCased CSS properties, not a CSS string: change <div style="color: red" /> to <div style={{ color: 'red' }} />, and const s = 'color: red' to const s = { color: 'red' }. If the value comes from a typed variable, widen or correct its type so it can only hold an object (or null/undefined). For a genuinely custom component that accepts string styles: whether rendered via JSX or React.createElement(StatusBar, { style: 'auto' }): add its name to the rule's allow setting rather than reshaping the value, since the createElement path checks capitalized components too. See https://oxc.rs/docs/guide/usage/linter/rules/react/style-prop-object

Repository-wide copy prompt

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