react-doctor/no-wide-letter-spacing
Reserve wide tracking (letter-spacing > 0.05em) for short uppercase labels, navigation items, and buttons: not body text
- Status
- Active
- Category
- Architecture
- Assessment
- Evidence-required risk
- Required evidence
- source code, repository context, rendered UI, product intent
- Default configuration
- Disabled until configured
- Default severity
- warn
Show technical metadata
- Scope
- All supported frameworks
- Active when
- always
- Tags
- design, test-noise
- Priority
- 12 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Confirm style.letterSpacing is greater than 0.05em AND the element does NOT have textTransform: 'uppercase'. The rule normalizes bare numbers and Npx to em assuming a 16px base.
Suppress when: stylized hero brand-mark text where wide tracking is part of the established typographic system.
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.
The design tag controls activation and discovery. It does not determine the rule’s proof class.
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.
Remove letterSpacing (typefaces ship with optimal tracking) or pair wide tracking with textTransform: 'uppercase' on short labels, nav items, and pill buttons. For display sizes, slightly negative tracking often reads tighter and more polished than positive tracking. See https://practicaltypography.com/letterspacing.html
Repository-wide copy prompt
Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.
Show repository-wide prompt
Fix every confirmed react-doctor/no-wide-letter-spacing diagnostic in the current repository.
Required change:
- Remove letterSpacing (typefaces ship with optimal tracking) or pair wide tracking with textTransform: 'uppercase' on short labels, nav items, and pill buttons. For display sizes, slightly negative tracking often reads tighter and more polished than positive tracking. See https://practicaltypography.com/letterspacing.html.
Validation before editing:
Confirm style.letterSpacing is greater than 0.05em AND the element does NOT have textTransform: 'uppercase'. The rule normalizes bare numbers and Npx to em assuming a 16px base.
Suppress when: stylized hero brand-mark text where wide tracking is part of the established typographic system.
Constraints:
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.