VolatilitySmileChart
Read a market, a risk or a return, with the axis and the tooltip wired for the job.
@luc/ui/chartsWhat it shows
Show implied volatility by strike for one or more expiries, making the smile or skew visible.
Live preview
Strike on a numeric axis, one curve per expiry. Volatility is declared with its own percent suffix.
<VolatilitySmileChart
slices={[
{
expiry: "1M",
points: [
{ strike: 90, impliedVol: 24.1 },
{ strike: 95, impliedVol: 20.4 },
{ strike: 100, impliedVol: 18.6 },
{ strike: 105, impliedVol: 19.2 },
{ strike: 110, impliedVol: 21.8 },
],
},
{
expiry: "3M",
points: [
{ strike: 90, impliedVol: 22.4 },
{ strike: 95, impliedVol: 19.6 },
{ strike: 100, impliedVol: 18.1 },
{ strike: 105, impliedVol: 18.9 },
{ strike: 110, impliedVol: 20.7 },
],
},
]}
strikeFormat={{ kind: "number", decimals: 0 }}
volFormat={{ kind: "number", decimals: 1, suffix: "%" }}
height={340}
ariaLabel="Volatility by strike"
/>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 { VolatilitySmileChart } from "@luc/ui/charts";
<VolatilitySmileChart
slices={[
{
expiry: "1M",
points: [
{ strike: 90, impliedVol: 24.1 },
{ strike: 95, impliedVol: 20.4 },
{ strike: 100, impliedVol: 18.6 },
{ strike: 105, impliedVol: 19.2 },
{ strike: 110, impliedVol: 21.8 },
],
},
{
expiry: "3M",
points: [
{ strike: 90, impliedVol: 22.4 },
{ strike: 95, impliedVol: 19.6 },
{ strike: 100, impliedVol: 18.1 },
{ strike: 105, impliedVol: 18.9 },
{ strike: 110, impliedVol: 20.7 },
],
},
]}
strikeFormat={{ kind: "number", decimals: 0 }}
volFormat={{ kind: "number", decimals: 1, suffix: "%" }}
height={340}
ariaLabel="Volatility by strike"
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 `VolatilitySmileChart` from Luc UI. It is: Read a market, a risk or a return, with the axis and the tooltip wired for the job.
Import it with: import { VolatilitySmileChart } 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={340}`, `state="ready"`, `ariaLabel="Volatility by strike"`.
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
<VolatilitySmileChart
slices={[
{
expiry: "1M",
points: [
{ strike: 90, impliedVol: 24.1 },
{ strike: 95, impliedVol: 20.4 },
{ strike: 100, impliedVol: 18.6 },
{ strike: 105, impliedVol: 19.2 },
{ strike: 110, impliedVol: 21.8 },
],
},
{
expiry: "3M",
points: [
{ strike: 90, impliedVol: 22.4 },
{ strike: 95, impliedVol: 19.6 },
{ strike: 100, impliedVol: 18.1 },
{ strike: 105, impliedVol: 18.9 },
{ strike: 110, impliedVol: 20.7 },
],
},
]}
strikeFormat={{ kind: "number", decimals: 0 }}
volFormat={{ kind: "number", decimals: 1, suffix: "%" }}
height={340}
ariaLabel="Volatility by strike"
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: Financial & quantitative
import { VolatilitySmileChart } from "@luc/ui/charts";<VolatilitySmileChart
slices={[
{
expiry: "1M",
points: [
{ strike: 90, impliedVol: 24.1 },
{ strike: 95, impliedVol: 20.4 },
{ strike: 100, impliedVol: 18.6 },
{ strike: 105, impliedVol: 19.2 },
{ strike: 110, impliedVol: 21.8 },
],
},
{
expiry: "3M",
points: [
{ strike: 90, impliedVol: 22.4 },
{ strike: 95, impliedVol: 19.6 },
{ strike: 100, impliedVol: 18.1 },
{ strike: 105, impliedVol: 18.9 },
{ strike: 110, impliedVol: 20.7 },
],
},
]}
strikeFormat={{ kind: "number", decimals: 0 }}
volFormat={{ kind: "number", decimals: 1, suffix: "%" }}
height={340}
ariaLabel="Volatility by strike"
/>Data contract
`slices` each contain an `expiry` and `points` of `{ strike, impliedVol }`. Volatility is a supplied value already in the displayed unit, not a price or a computed model parameter.
Important configuration
Use `strikeFormat` for the strike axis, `volFormat` for the percent or decimal convention, and keep expiries ordered and labelled.
Guidelines
When not to use
Do not feed option prices in place of implied volatility or interpolate a smooth surface without showing the observed strikes.
Configuration
| Export | Kind | Signature |
|---|---|---|
VolatilitySmileChart | 13 documented props | ({ slices, strikeFormat, volFormat, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: VolatilitySmileChartProps) => import("@types/react").JSX.Elem… |
VolatilitySmileChart props
Type: VolatilitySmileChartProps
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. |
height? | string | number | undefined | — | |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
slices | readonly VolatilitySlice[] | — | |
state? | ChartState | undefined | — | |
strikeFormat? | ChartFormat | undefined | — | |
title? | string | undefined | — | |
volFormat? | ChartFormat | undefined | — | Implied volatility, already in the caller's units (e.g. 0.42 or 42). |
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
Financial & quantitative
Presentation only: not one metric here is computed by the library.
Related