New
Introducing React Bench, see how different models perform on React code

react-doctor/no-flat-page-type-scale

Page typography uses a compressed size range

  • Category: Maintainability
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: always
  • Tags: design, test-noise
  • Default: Disabled until configured

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-flat-page-type-scale. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

<main>
  <h1 className="text-lg">Report</h1>
  <h2 className="text-base">Findings</h2>
  <p className="text-sm">Details</p>
</main>;

Corrected pattern

<main>
  <h1 className="text-4xl">Report</h1>
  <h2 className="text-2xl">Findings</h2>
  <p className="text-base">Details</p>
</main>

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/no-flat-page-type-scale diagnostic in the current repository. Required change: - Use a clearer size hierarchy when a page declares several explicit typography steps.
Reference transformation:Before:
<main>
  <h1 className="text-lg">Report</h1>
  <h2 className="text-base">Findings</h2>
  <p className="text-sm">Details</p>
</main>;
After:
<main>
  <h1 className="text-4xl">Report</h1>
  <h2 className="text-2xl">Findings</h2>
  <p className="text-base">Details</p>
</main>
Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Use existing brand assets, product facts, content, and design tokens. - Do not invent claims, customer data, typefaces, or artwork. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Maintainability rules from the rules reference: