## 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/maybloc/1877ee03-3cf3-49f7-b006-226ca2ea42de-1792217043-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/maybloc/1877ee03-3cf3-49f7-b006-226ca2ea42de-1792216974687-full.webp
- Component on Kage: https://kage.design/component/maybloc-cta

## Before you start
Ask what the user's product is, who it serves, and what brand voice and visual identity it should use. Apply the principles below to that product rather than reproducing the reference.

Create a developer CTA as a generous two-column section. On the left, use a large serif headline, a short explanation of the integration flow, a small outlined copyable snippet/control with a copy icon and feedback state, and a dark rounded docs/action button. On the right, place an original abstract code or API-themed object with a restrained shadow. Use near-white #fafafa, #111111 headings, #6f6f6f body text, #e5e5e5 borders, 12–16px radius, and pill-shaped buttons. The copy control should have hover, focus, and copied states; the primary action should be visually dominant. Stack on mobile and place the visual below the actions.

Never: use the reference's logo, product name, copy, illustrations, imagery, or exact API language.