## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/lull/1eb36b3c-9a0d-499b-8ae4-8916c2d1f7b6-1789884097-4.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/lull/1eb36b3c-9a0d-499b-8ae4-8916c2d1f7b6-1789884066726-full.webp
- Component on Kage: https://kage.design/component/lull-tabs

## Before you start
Ask what recurring behavior, data, or progress the user's product helps people understand. Use that to design a focused product-demonstration section.

Build a dark, immersive feature section with a centered eyebrow and serif question or benefit headline. The primary visual should be a polished, compact product interface such as a calendar, timeline, tracker, or other relevant visualization. Place it inside a translucent dark panel with a soft border and generous internal padding. Beneath the interface, add three concise explanatory items in a horizontal row, each with a small circular icon, bold label, and one short supporting sentence. If multiple views exist, make the interface tabs or segmented controls, but keep the default view immediately understandable.

Use #080909 as the base, image or gradient texture behind it, panel rgba(255,255,255,.07), border rgba(255,255,255,.14), 16px radius, muted text #9e9b96, highlight color selected from the user's brand. Keep the calendar/data visualization low contrast with one restrained accent. Desktop layout is centered with a max width around 700px; supporting items use three equal columns and collapse cleanly on mobile.

### Never
- Never reproduce the reference calendar, labels, dates, copy, logo, or product name.
- Never expose dense data without a clear legend or meaning.
- Never use decorative charts that do not support the user's product story.