react-doctor/no-many-boolean-props

Split into compound components or named variants: `<Button.Primary />`, `<DialogConfirm />` instead of stacking `isPrimary`, `isConfirm` flags

Validation prompt

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

Fires when a component accepts 4 or more props whose names match is|has|should|can|show|hide|enable|disable|with followed by an uppercase letter (e.g. isPrimary, hasIcon, showHeader, canEdit). Both destructured ({ isPrimary }) and props.isPrimary member-access forms are detected. The name-based heuristic can catch non-boolean props using those prefixes (e.g. withIconSize: number), so confirm they really are mutually-exclusive booleans.

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.

Replace the flags with a discriminated variant prop (variant: "primary" | "danger") or split into compound subcomponents (<Button.Primary />, <DialogConfirm />) so consumers select one explicit shape rather than juggling mutually-exclusive booleans. Compound components fit best when variants share most internals but differ in slot composition. See https://kentcdodds.com/blog/compound-components-with-react-hooks

Repository-wide copy prompt

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