## 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/tiun/82cad29c-5bdb-4fc9-91ef-0bee36475f7f-1789538801-9.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/tiun/82cad29c-5bdb-4fc9-91ef-0bee36475f7f-1789538671428-full.webp
- Component on Kage: https://kage.design/component/tiun-chart

## Before you start
Ask which teams use the user's analytics, what questions they ask, and how an assistant or workflow should turn data into action. Design an original analytics experience.

Create an analytics section with a strong headline, a brief supporting sentence, and a horizontal role/tab selector. Give the active tab a small violet underline or glow while inactive tabs remain gray. Below, build a centered dark insight workspace: a compact question chip, a short status line, an assistant response, and a prompt composer with suggestion pills and a clear submit control. Use #050505, panels #0D0D0D, borders #202020, white text, gray #858585, and violet #8B5CF6 for active states. Keep the interface calm and spacious, with 12–16px radii and subtle transitions on tabs and buttons.

Never: use the reference logo, product name, exact copy, illustrations, or imagery.