Preview the prompt +
# Build brief — an original faq section in the taste of Function Health
> Reference: [screenshot](https://uidiscovery.com/media/captures/function-health/s-12.webp) (2200×1179, 1440px viewport @2x) · UIDiscovery: https://uidiscovery.com/sections/function-health-12 · source https://www.functionhealth.com
## Goal
Build an original faq section for **[the user's brand]**. Its job: remove the last objections before the call to action.
## Originality rules
- Never reuse Function Health's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
## Layout
- Pattern: question list with disclosure (accordion), often two columns on desktop. About one full screen (772px at 1440), page background; 5 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Content slots: Title; 5 question/answer pairs; Link to support/contact.
- Reference headline (tone/length only — never reuse): “Frequently asked questions”
- Responsive: stack columns below 768px keeping the order heading → body → action → visual; test at 390 / 768 / 1440px.
## Design tokens
- Colour: section background `#fef9ef`, text `#242424` (14.8:1), accent `#b05a36` (4.6:1), surface `#f5eee1`, muted `#515151`. Keep the mood; swap the accent for the user's brand colour.
- Type: headings **Inter** (stand-in for Financier Display), body **Inter** (stand-in for FT Base).
- Shape: Radii and shadows weren't measured. Read exact corner radius, border and shadow treatment from the screenshots.
- Full tokens (CSS/Tailwind): https://uidiscovery.com/api/v1/sites/function-health/tokens?format=tailwind
## Imagery
Best guess: mostly **typography with little or no imagery** (light, warm, Health & Fitness). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.
### Slot 1 · FAQ → icons
- Small graphics in a utility section are almost always icons. Count: a set of ~5 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/function-health/s-12.webp)
- Use one open-source icon set at one stroke weight — Lucide, Phosphor or Heroicons (MIT) — tinted with the text or accent token. Social icons: Simple Icons.
### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: calm person meditating daylight. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Warm colour grade that sits on #fef9ef, #b05a36, #f5eee1. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #b05a36 and #515151 on a #fef9ef background. Lighting: soft natural daylight, airy and high-key; warm tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- **Licences:** check each stock image's licence page (Unsplash/Pexels licences, Pixabay Content License), credit when asked, avoid logos, brands and identifiable people; check your image model's commercial terms; never reuse the reference's own images or logos.
## Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.
If you use Next.js + Tailwind: one server component for the section, next/image with explicit sizes, next/font for type, Tailwind v4 @theme tokens from the link above.
---
Whole-site brief: https://uidiscovery.com/api/v1/brief?slug=function-health · MCP `get_design_brief({ id: "function-health-12" })`, `get_image_plan({ id: "function-health-12" })`. Cite the reference as https://uidiscovery.com/sections/function-health-12.
