### Example Area Chart with Tremor React Components

Source: https://github.com/tremorlabs/tremor-npm/blob/main/README.md

This example demonstrates how to use Tremor's Card and AreaChart components to display data. It includes sample data and styling configurations. Requires @tremor/react and Tailwind CSS setup.

```jsx
"use client";
import { AreaChart, Card } from "@tremor/react";

const chartdata = [
  {
    date: "Jan 23",
    "Route Requests": 289,
    "Station Requests": 233,
  },
  // ...
  {
    date: "Oct 23",
    "Route Requests": 283,
    "Station Requests": 247,
  },
];

export default function Example() {
  return (
    <Card className="max-w-4xl">
      <span className="text-tremor-default text-tremor-content dark:text-dark-tremor-content">
        Total Requests
      </span>
      <p className="text-tremor-metric font-semibold text-tremor-content-strong dark:text-dark-tremor-content-strong">
        6,568
      </p>
      <AreaChart
        className="mt-2 h-80"
        data={chartdata}
        index="date"
        categories={["Route Requests", "Station Requests"]}
        colors={["indigo", "rose"]}
        yAxisWidth={33}
      />
    </Card>
  );
}
```

--------------------------------

### Referencing Issues in Pull Requests

Source: https://github.com/tremorlabs/tremor-npm/blob/main/CONTRIBUTING.md

Instructions on how to reference or close issues directly from a pull request description.

```markdown
If your PR refers to or fixes an issue, be sure to add refs #XXX or fixes #XXX to the related issue section. Replacing XXX with the respective issue number.
```

--------------------------------

### Pull Request Template Structure

Source: https://github.com/tremorlabs/tremor-npm/blob/main/CONTRIBUTING.md

This outlines the required structure for a pull request description, ensuring all necessary information is provided for review.

```markdown
1. Description: Describe your changes in detail.
2. Related issue(s): Please link to the issue.
3. What kind of change does this PR introduce?: Select from template options.
4. Does this PR introduce a breaking change?: Select Yes/No.
5. How has This been tested?: Please describe how you tested your changes.
6. Screenshots (if appropriate):
```

--------------------------------

### Branch Naming Conventions

Source: https://github.com/tremorlabs/tremor-npm/blob/main/CONTRIBUTING.md

Defines the standard prefixes for Git branches to categorize the type of changes being made.

```markdown
- `fix/` for bug fixes
- `feat/` for features
```

--------------------------------

### Pull Request Requirements Checklist

Source: https://github.com/tremorlabs/tremor-npm/blob/main/CONTRIBUTING.md

A checklist to ensure a pull request meets the project's contribution standards before submission.

```markdown
- [ ] It's submitted to the `main` branch.
- [ ] When resolving a specific issue, it's referenced in the related issue section above.
- [ ] My change requires a change to the documentation. (Managed by Tremor Team).
- [ ] I have added tests to cover my changes.
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.