Skip to content

Hero & Bento Visuals

Editorial Glassmorphic Bento Grid & Isometric Lighting Prompt

One image prompt that generates matching dark and cream SaaS hero graphics (same light direction, materials and palette), plus the bento shell to drop them into.

Dark + cream · Cohesive

Works in Webflow Framer React Zero CLS

Customize before you copy

Platform

Showing the Webflow version

Claude prompt · production spec
Act as an art director for a premium SaaS brand. Write me a set of image-generation prompts for hero and bento graphics that all look like one family, plus the layout they'll sit in.

Brand system (use exactly):
- Palette: warm cream #F6F4EF, warm sand #B59E7A, deep charcoal #141413, one muted sage accent #6E8B74. No saturated blues or purples.
- Materials: frosted glass panels with 1px light edges, soft paper-grain on cream surfaces, brushed matte charcoal.
- Lighting: a single soft key light from the top-left at 45°, long gentle shadows to the bottom-right, a faint warm rim light on glass edges. Same direction in every image.
- Camera: isometric 3/4 view, 30° elevation, orthographic feel, no lens distortion.
- Composition: a bento of 4–6 floating glass UI cards (chart, toggle, avatar stack, progress ring, code line) with generous negative space on the left third for headline copy.

Produce:
1. A master prompt for the cream (light) hero, 16:9.
2. The same prompt adapted for a charcoal (dark) hero, keeping lighting and composition identical, only swapping surface values.
3. Three square (1:1) bento-tile prompts reusing the materials, one UI element each.
4. A negative prompt: no text, no logos, no people, no neon, no lens flare, no clutter.
5. Export sizes for each image and how to place them in the bento grid without layout shift.

Write each prompt as one paragraph, front-loading subject, then materials, lighting, camera and palette. End with --ar and quality flags for Midjourney v7 and a plain-language variant for other models.

Target platform: Webflow.
- Build the structure as native Webflow Designer elements with Client-First class names (section_[name], [name]_component, [name]_item). No div soup from an HTML embed unless I ask for one.
- Hook every behaviour to custom attributes (data-gsap="…"), never to class names, so designers can restyle without breaking the script.
- Load GSAP through Webflow's built-in GSAP integration (Site settings) or the jsDelivr CDN tags, and put the init script in Page settings → Before </body> tag, wrapped in Webflow.push(() => { … }).
- Say which parts go in Designer styles, which in a page-head <style>, and which in the body script.
- Bento shell as Designer elements: section_bento > bento_grid > bento_tile (combo classes is-hero / is-wide). Images as Webflow Image elements with explicit width/height; export 2× PNG and let Webflow serve WebP/AVIF.

3-step implementation guide

  1. Step 1

    DOM & attribute setup

    Write down your exact palette, one light direction and one camera angle before generating anything. Those three constants are what make separate images read as one family.

  2. Step 2

    Prompt Claude or drop in the snippet

    Paste the prompt to get the light master, the dark master and the tile prompts. Generate, keep the best seed, and reuse it for every variation. Drop the results into the bento shell for your platform.

  3. Step 3

    Mobile & Core Web Vitals check

    Export at 2× the displayed size and let the platform serve WebP/AVIF. Give every tile a fixed aspect ratio so images load without shifting, and confirm the hero image isn't lazy-loaded if it's your LCP.

Building a full site like this?

Skip the manual setup — I ship complete Figma-to-Webflow & Framer builds in 5–10 business days, or can wire this exact interaction into your live site in 48 hours ($250).