Load Rhythm
Prov1.0.0When the week's load lands, and a draggable maintenance window that finds the quietest hours.
Build for your project
Code/install build
Usage
Import it and pass your content. The props that matter most are listed next.
Example
import { LoadRhythm, type MaintenanceWindow, type RhythmMetric } from "@/components/ui/notchset/blocks/load-rhythm";
export function Rhythm({ metrics }: { metrics: RhythmMetric[] }) {
return (
<LoadRhythm
title="Load rhythm"
metrics={metrics}
onSchedule={async (w: MaintenanceWindow) => {
await fetch("/api/maintenance", { method: "POST", body: JSON.stringify(w) });
}}
/>
);
}Props
metrics–{ id, label, values, previous, hot?, riseIsBad? }[]values: seven days (Monday first) of 24 hourly numbers; hot marks values above it in signal.
lengths / zone–number[] / stringWindow lengths in hours (2, 4, 6) and the zone label (UTC).
onSchedule–({ day, start, hours }) => Promise<void>Book the window (day is null for every day).
Anatomy
- Focusing a day scopes the window's share and the quietest window to that day.
- A window carrying more than 12% of the load reads in signal.
- Clicking a dot pins its value in the aside.
LoadRhythmdata-slot="load-rhythm"Controls, the dot grid with its window slider, and the aside.
Source
components/ui/notchset/blocks/load-rhythm.tsx
This component is included with Pro.
Try the live preview above. Get Pro to install the source.
Build for your project
Code/install build
Installation
pnpm dlx shadcn@latest add @beautiful-ui-pro/load-rhythmNeeds your registry key. Your components.json style picks the Base UI or Radix build: radix-*, new-york and default get Radix, base-* gets Base UI.
Styles didn't apply?
The CLI adds the styles to the CSS file named in components.json (tailwind.css). Check that it points at your global stylesheet, that the project uses Tailwind CSS v4, and that the file is imported in your root layout. Installed by hand: paste styles.css into that file.
For coding agents
Give your coding assistant the Markdown guide instead of screenshots.
Use it for
- Seeing when a service is busiest across a week
- Choosing a maintenance or deploy window
Use something else when
- A single day's timeline: use a line chart
- Months of history: use an activity heatmap
Mistakes to avoid
- Pass hours in one zone and label it
- Keep the values hourly; the grid is always 7×24
Agents find it by
- traffic heatmap, punch card, hour of day, day of week, maintenance window, load pattern, ops, Notchset
Where agents read it
- Guide for this component: https://beautiful-ui.dev/md/load-rhythm.md
- Every component, for tools without MCP: /llms.txt
- MCP server:
https://beautiful-ui.dev/api/mcp(setup)
Behaviour
Keyboard
- ← → / Page Up / Page Down
- Move the window
- Home / End
- Window to the start or end of the day
Accessibility
- The chart is an image labelled with the window and its share of load
- The window is a slider (arrows ±1 hour, Page Up / Down ±3, Home / End) with time value text
- Day labels are toggle buttons that focus one day
Motion
- WEEK ↔ STACKED
- Every dot glides to its new place (700ms, staggered by hour and day)
- Window
- Glides on click and key presses; follows the pointer while dragged
- Numbers
- Totals and the window's share roll
Responsive
- Under 760px (container width) the aside stacks under the chart, which keeps 620px and scrolls sideways.
Performance
- 168 SVG circles moved by CSS transitions; nothing runs while idle.
Changelog
v1.0.0 · 2026-10-04
First release
Part of
Included with Pro
Pro is in early access.
