SlopeChart
Show sequence, schedule or attribution over rows you prepared.
@luc/ui/chartsWhat it shows
Show rank or level movement between two periods, where crossing lines communicate a change in order.
Live preview
Ranks rather than levels: lines are free to cross, and the crossing is the finding.
<SlopeChart
rows={[
{ label: "Momentum", left: 1, right: 3, tone: "warning" },
{ label: "Value", left: 2, right: 1, tone: "positive" },
{ label: "Carry", left: 3, right: 2, tone: "accent" },
{ label: "Quality", left: 4, right: 4, tone: "neutral" },
]}
periods={["Q1", "Q2"]}
format={{ kind: "integer" }}
height={300}
ariaLabel="Rank movement"
/>Controls
Height
A chart measures its container, so it always needs a definite height.
State
The surface the chart is in — loading, empty and error are drawn by the component.
Accessible name
A drawing is not readable by a screen reader, so it needs a name that states what it shows.
The same fixture as the live preview above; the controls change how it is drawn, not what it measures.
Code
import { SlopeChart } from "@luc/ui/charts";
<SlopeChart
rows={[
{ label: "Momentum", left: 1, right: 3, tone: "warning" },
{ label: "Value", left: 2, right: 1, tone: "positive" },
{ label: "Carry", left: 3, right: 2, tone: "accent" },
{ label: "Quality", left: 4, right: 4, tone: "neutral" },
]}
periods={["Q1", "Q2"]}
format={{ kind: "integer" }}
height={300}
ariaLabel="Rank movement"
state="ready"
/>Not controllable here
series / rows— The numbers are the caller's; the fixture above is the example.
Copy for an AI agentA specification an agent can act on: the import, the setup, the chosen props, the data contract and the accessibility expectation.
Implement `SlopeChart` from Luc UI. It is: Show sequence, schedule or attribution over rows you prepared.
Import it with: import { SlopeChart } from "@luc/ui/charts";
Requires: react ^19.0.0; react-dom ^19.0.0; react-hook-form ^7.0.0 (optional, for @luc/ui/forms/react-hook-form); tailwindcss ^4.0.0; node >= 22 (repository tools). Import the stylesheet once at the app root and wrap the tree in `LucProvider`. Both come from the package that publishes @luc.
Chosen configuration: `height={300}`, `state="ready"`, `ariaLabel="Rank movement"`.
Accessibility: keep the component's own semantics. Do not re-implement its ARIA wiring, do not add roles it does not declare, and make sure every interactive element is reachable and operable from the keyboard with a visible focus state.
Styling: use Luc UI design tokens and the component's own props. Do not restyle with raw colour literals and do not override the component's internal structure with page CSS.
Motion: respect `prefers-reduced-motion`. The component already does, so do not disable it.
Reproduce this state:
```tsx
<SlopeChart
rows={[
{ label: "Momentum", left: 1, right: 3, tone: "warning" },
{ label: "Value", left: 2, right: 1, tone: "positive" },
{ label: "Carry", left: 3, right: 2, tone: "accent" },
{ label: "Quality", left: 4, right: 4, tone: "neutral" },
]}
periods={["Q1", "Q2"]}
format={{ kind: "integer" }}
height={300}
ariaLabel="Rank movement"
state="ready"
/>
```Usage
The values are prepared by the caller: this component draws the points it is given and computes no statistic of its own, so units, scaling and any summary have to be settled before the data reaches it.
It is drawn by the ECharts engine.
Worked examples with real data are on the family overview: Workflow & operations
import { SlopeChart } from "@luc/ui/charts";<SlopeChart
rows={[
{ label: "Momentum", left: 1, right: 3, tone: "warning" },
{ label: "Value", left: 2, right: 1, tone: "positive" },
{ label: "Carry", left: 3, right: 2, tone: "accent" },
{ label: "Quality", left: 4, right: 4, tone: "neutral" },
]}
periods={["Q1", "Q2"]}
format={{ kind: "integer" }}
height={300}
ariaLabel="Rank movement"
/>Data contract
`rows` contain `label`, `left` and `right` numeric values; `periods` names the two endpoints; `format` names the value or rank scale. Values must be comparable.
Important configuration
Use rank formats when the values are ranks, keep period names explicit, and use tone to identify the series that changed most.
Guidelines
When not to use
Do not use a slope chart for more than two periods or for many crossings that become unreadable.
Configuration
| Export | Kind | Signature |
|---|---|---|
SlopeChart | 13 documented props | ({ rows, periods, format, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: SlopeChartProps) => import("@types/react").JSX.Element |
SlopeChart props
Type: SlopeChartProps
Values the compiler reads from the declaration.
| Prop | Type | Default | Notes |
|---|---|---|---|
ariaDescription? | string | undefined | — | |
ariaLabel? | string | undefined | — | |
className? | string | undefined | — | |
description? | string | undefined | — | |
eager? | boolean | undefined | — | Create the engine on mount rather than when the surface is approached. |
format? | ChartFormat | undefined | — | |
height? | string | number | undefined | — | |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
periods? | readonly [string, string] | undefined | — | The two period labels drawn under the two columns. |
rows | readonly { label: string; left: number; right: number; tone?: SeriesTone; }[] | — | |
state? | ChartState | undefined | — | |
title? | string | undefined | — |
Accessibility
A chart is a picture of data, so it needs a name that states what it shows, and the numbers must exist as text somewhere on the page — in a table or a written summary — because a drawing is not readable by a screen reader and cannot be copied.
What happens on the server, and when hydration changes it.
Family
Workflow & operations
Sequence, schedule, comparison and attribution.
Related