## 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/thinking-orbs/1e178b90-85cc-40c4-86e5-bc16130bc9ab-1791180318-5.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/thinking-orbs/1e178b90-85cc-40c4-86e5-bc16130bc9ab-1791180214590-full.webp
- Component on Kage: https://kage.design/component/thinking-orbs-code-block-3

## Before you start
Ask what the user's product and brand are, then apply the principles below to that product rather than reproducing the reference.

Create a closing documentation section that explains optional extension points for a visual component. Use a small white heading, two or three lines of muted body copy, then a compact rounded code panel with restrained syntax highlighting. Keep the same narrow column and dark palette: #030303 background, #171717 code surface, #242424 border, #d8d8d8 primary text, #777777 secondary text, and a small lavender/cyan/green syntax palette. Finish with a subtle underlined resource link or next-step action. Maintain generous spacing and ensure code is scrollable and copyable, with reduced-motion behavior if the example contains animation.

Never: use logos, product names, copy, illustrations, or imagery from the reference.