react-doctor/forbid-elements

Replace each configured forbidden element with its sanctioned component or wrapper.

Validation prompt

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

Fires only when the forbidElements.forbid setting is non-empty, then reports any JSX opening element whose flattened name (e.g. button, Modal, dotted.Component) is in that list, plus matching React.createElement(...) / bare createElement(...) calls whose first argument resolves to a forbidden name. createElement string args only match if they look like a real DOM tag: lowercase first char and no dots: while identifier args match only when PascalCase or leading-underscore, and member expressions match by flattened name.

Suppress when: it cannot tell apart two distinct things sharing a name, so a forbidden button entry also flags a legitimate local component or third-party export that happens to be named identically.

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.

Swap the forbidden element for the sanctioned replacement named in the finding's message, e.g. replace <button> with your design-system <Button> (and likewise rewrite React.createElement("button", ...) to React.createElement(Button, ...)). If a flagged usage is a genuine, intentional exception, remove that entry from the forbidElements.forbid setting or add an inline disable with a written justification rather than suppressing project-wide. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-elements

Repository-wide copy prompt

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