## 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/codeaf/74fffb9e-aea6-4193-af2d-c8a5b19c270c-1791007530-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/codeaf/74fffb9e-aea6-4193-af2d-c8a5b19c270c-1791007420738-full.webp
- Component on Kage: https://kage.design/component/codeaf-cta

## Before you start
Ask what the user's primary activation action is, what command or form starts it, and which secondary guide or community destination reduces friction. Apply the following conversion pattern with their product and voice.

Create a dark closing CTA with a compact community strip or utility link at its top, followed by a centered or left-aligned heading, one-sentence reassurance, and a bordered command/install control with copy affordance plus a secondary guide button. Include a small row of trust or community links beneath. Keep the CTA direct and practical rather than promotional.

Design language: #08090a background, heading #e0e2df around 24–28px, supporting text #777b79 at 12–13px, borders #30312d, and warm amber #bd9746 for the smallest accent. Use a terminal-style monospace field at 11–12px, 8px radius or square corners, 44–48px control height, and 12px gaps. Primary action may use a subtly lighter dark fill; secondary action remains outlined. Add copy confirmation feedback and responsive wrapping for narrow screens.

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