# `react-doctor/no-nested-card-surface`

Card surface is nested inside another card

- **Category:** Maintainability
- **Severity:** warn
- **Source:** oxlint-plugin-react-doctor
- **Framework:** global
- **Enabled when:** tailwind

## Validate the diagnostic

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

Confirm the reported code matches `react-doctor/no-nested-card-surface`. 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

```tsx
<article className="rounded-xl border p-6">
  <section className="rounded-xl border p-4">Details</section>
</article>;
```

### Corrected pattern

```tsx
const Example = () => (
  <div className="rounded-xl border p-6">
    <section className="border-t pt-4">Inner</section>
  </div>
);
```

## 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.

````text
Fix every confirmed `react-doctor/no-nested-card-surface` diagnostic in the current repository.

Required change:
- Flatten the inner surface and use spacing, a divider, or typography to communicate the hierarchy.

Reference transformation:

Before:
```tsx
<article className="rounded-xl border p-6">
  <section className="rounded-xl border p-4">Details</section>
</article>;
```

After:
```tsx
const Example = () => (
  <div className="rounded-xl border p-6">
    <section className="border-t pt-4">Inner</section>
  </div>
);
```

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.
- Confirm this rule is enabled for the project: `tailwind`.

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.
````