## 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/peras/2c988a48-c598-4fdf-86c9-23be8072f64d-1792821848-11.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/peras/2c988a48-c598-4fdf-86c9-23be8072f64d-1792821751917-full.webp
- Component on Kage: https://kage.design/component/peras-footer

## Before you start
Ask what brand identity, resource links, legal requirements, and closing message the user's product needs. Apply the following structure with original content.

Build a dark footer separated from the FAQ by generous spacing and a subtle top rule. Use a constrained inner width with the brand and a one-line closing statement on the left, and a compact row or cluster of documentation, source, package, and policy links on the right. Add a lower divider and a final row containing copyright/project attribution and a concise affiliation or disclaimer. Use #080b0a background, #eef1eb primary text, #919a91 muted text, #252c26 dividers, and lime for the brand accent. Use 13–15px body text, underlined or clearly interactive links, 40–64px top padding, and responsive stacking on small screens.

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