react-doctor/hook-use-state

Destructure useState as `const [thing, setThing] = useState(…)`.

Validation prompt

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

Fires on a useState() call that isn't destructured into exactly a two-element array [value, setter] whose setter is a plain identifier named set<Value>: flagging non-destructured const x = useState(), wrong arity [a, b, c], an object/array pattern in the setter slot [res, {}], a destructured value [{ res }, setRes] (unless settings react-doctor.hookUseState.allowDestructuredState is true), value names that don't start with a lowercase letter like RGB (no set<X> is derivable), and mismatched setters like [color, updateColor]. A bare return useState(...) is exempt.

Suppress when: idiomatic patterns the convention deliberately breaks: the unused-marker const [count, _setCount] and the create-once const [instance] = useState(() => new Foo()) where the setter is intentionally omitted.

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.

Rename the pair to the symmetric convention const [thing, setThing] = useState(…) so the setter is set + the capitalized value name ([color, setColor], not [color, updateColor]). Use a value name starting with a lowercase letter so a set<X> form exists ([rgb, setRgb] rather than [RGB, setRGB]), and destructure into exactly two identifier elements: for an object/array initial value keep [state, setState] and read fields off state, or opt into react-doctor.hookUseState.allowDestructuredState if you genuinely want [{ res }, setRes]. See https://oxc.rs/docs/guide/usage/linter/rules/react/hook-use-state

Repository-wide copy prompt

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