Bruno Simon — 3D / WebGL Hero

3D / WebGLVisit sitebruno-simon.com

A real-time interactive 3D world as the interface — playful, technical, unforgettable.

Bruno Simon — 3D / WebGL Hero — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Motion

Design notes

Mood: Wow-factor, experimental, virtuosic. Interactive as the whole point. Portfolio-as-experience.
Colors: Scene-driven (often a bright playful sky + toy palette, or moody dark 3D). Cohesive within the 3D world.
Type: Minimal HTML type overlaid on the canvas; simple bold sans for the few labels. Type defers to the 3D.
Layout: Full-screen WebGL canvas as the page; navigation and content are objects within the scene or minimal overlaid UI.
Motion: Physics, drivable/explorable 3D, cursor and scroll drive camera/objects, particles, real-time lighting. Motion is the product.
Texture: 3D materials, shadows, lighting, particles, post-processing. Everything is rendered, not flat.
Imagery: Real interactivity is coded (three.js / WebGL). Generate supporting assets: matcap/texture maps, a skybox or gradient environment, and toy-model concept art. Tool: kie-ai for textures and concept art; hand-build the 3D scene in code.
Don't: No static hero image pretending to be 3D, no heavy text walls over the canvas. Keep overlaid UI minimal.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Bruno Simon — 3D / WebGL Hero
Source: https://bruno-simon.com
Swipefile reference: https://swipefile.design/ref/bruno-simon-webgl/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Wow-factor, experimental, virtuosic. Interactive as the whole point. Portfolio-as-experience.
- colors: Scene-driven (often a bright playful sky + toy palette, or moody dark 3D). Cohesive within the 3D world.
- typography: Minimal HTML type overlaid on the canvas; simple bold sans for the few labels. Type defers to the 3D.
- layout: Full-screen WebGL canvas as the page; navigation and content are objects within the scene or minimal overlaid UI.
- motion: Physics, drivable/explorable 3D, cursor and scroll drive camera/objects, particles, real-time lighting. Motion is the product.
- texture: 3D materials, shadows, lighting, particles, post-processing. Everything is rendered, not flat.
- dont: No static hero image pretending to be 3D, no heavy text walls over the canvas. Keep overlaid UI minimal.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Bruno Simon — 3D / WebGL Hero

Make it your own

Keep exploring