## 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/meetpaw/a0a465d2-81ef-4df0-b440-a946faf696c8-1792389688-4.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/meetpaw/a0a465d2-81ef-4df0-b440-a946faf696c8-1792389630481-full.webp
- Component on Kage: https://kage.design/component/meetpaw-faq

## Before you start
Ask what recurring objections or support questions users have about the user's product, and which answer should be expanded by default. Then build an original FAQ section using these principles.

Create a centered FAQ section with a short, bold heading around 32–40px and generous space above it. Constrain the accordion to a readable width of roughly 540–620px rather than spanning the whole page. Each item should be a full-width row separated by 1px lines in #e7e7e7, with 16–18px vertical padding, a 14–16px semibold question, and a chevron or plus icon aligned to the right.

Allow one item to be expanded initially. Its answer should use 14–15px line-height around 1.6, muted #6d6d6d text, and enough bottom spacing to remain readable. Use white or near-white background, dark #171717 text, and a restrained warm accent only for focus or active states. Animate height and icon rotation gently, support keyboard interaction, and expose proper ARIA accordion semantics. Keep the section padding large enough that it feels like a deliberate pause after the feature story.

### Never
- Never use logos, product names, copy, illustrations, or imagery from the reference.
- Never reuse the reference questions or answer wording.
- Never hide important pricing, privacy, or accessibility information only inside an inaccessible interaction.