## 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/oku-club/e710a983-c1d6-4177-b014-2738acd07d09-1789146245-10.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/oku-club/e710a983-c1d6-4177-b014-2738acd07d09-1789146208773-full.webp
- Component on Kage: https://kage.design/component/oku-club-footer

## Before you start
Ask what legal, support, social, and product links the user's footer needs and what accessibility requirements apply. Use the user's product and brand system.

Build a compact footer separated from the CTA by a very subtle top border. Place a single row of small navigation and legal links on the left or center, with a muted copyright or status line on the opposite side. Use generous horizontal padding, clear hover/focus states, and enough contrast for readability. On mobile, wrap links into two tidy rows and keep legal links easy to find.

Use white or `#f7f7f7`, near-black `#111111`, muted gray `#666666`, 12–13px type, 20–28px gaps, and a 1px border `#e8e8e8`. Keep the footer concise and avoid adding a large sitemap unless the product genuinely needs one.

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