## 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/raycast-2-0/585c4674-841f-40bf-a211-e6fd2d8f71e9-1789192911-7.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/raycast-2-0/585c4674-841f-40bf-a211-e6fd2d8f71e9-1789192849096-full.webp
- Component on Kage: https://kage.design/component/raycast-2-0-cta

## Before you start
Ask what the user's final conversion goal, CTA label, product promise, and compatibility constraints are. Apply these principles to that product rather than reproducing the reference.

Create a tall, centered closing CTA on a pure black background. Use a restrained two-line headline around 25px, with the first line in muted #9b9b9f and the emphasized line in #f1f1f2. Place a light neutral primary button (#f0f0f0) with dark text below, then a tiny muted compatibility note with generous spacing. Add a very subtle abstract product/device visual or layered geometric treatment in the lower portion, fading into the background via a black gradient; it should support the CTA without competing with it. Keep the composition vertically spacious and symmetric. The button needs a clear hover state and should remain prominent on mobile.

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