Lusion — WebGL Studio

The studio-portfolio answer to a scroll world: a physics-driven WebGL hero, then the 3D recedes and lets a perfectly ordinary case-study grid do its job, then it comes back for the finale.

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

Motion

Design notes

Mood

Technically flexing but commercially serious. Opens with a trick to prove capability, then gets straight to the work. Reads as a studio that ships, not an experiment.

Colors

Bright near-white paper for the content stretch, hard cut to true black for the WebGL beats. The 3D scenes carry saturated candy colour (electric blue, iridescent pinks) that never appears in the UI itself.

Type

Large tight-tracked geometric sans for statements, ~11px uppercase mono for project meta. Statements sit centred on their own screen with nothing else on it.

Layout

Alternating full-bleed 3D beats and conventional two-column content. The grid is a plain two-up of project cards — deliberately unremarkable, because it is the part that has to be readable.

Motion

Physics rather than a camera path: objects collide, tumble and settle under simulated forces, and the cursor pushes them. Scroll advances between beats while a decorative curve threads continuously behind the content.

Texture

Matcap and clearcoat plastics, soft studio lighting, real contact shadows, subtle bloom. Surfaces read as injection-moulded objects photographed in a studio.

Imagery

Two asset classes and they must not be confused. The hero and finale are real-time WebGL — build them in code. The case-study grid wants actual project stills and short muted loops, which is where a portfolio either convinces or doesn't. Tool: real client work if it exists, kie-ai concept renders if it doesn't; hand-build the 3D in three.js.

Don't

Don't run 3D under the case-study grid. The whole structure works because the effects stop when there is something to actually read, and start again when there isn't.

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 withAny AI toolCodexClaudeCursorChatGPTGeminiv0 / LovableI want toBuild a screenAudit my UIWrite a design brief

Tech stackUse the existing project stackReact / Next.jsAstroVue / NuxtSvelte / SvelteKitHTML / CSS / JavaScriptSwiftUIFlutter

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: Lusion — WebGL Studio Source: https://lusion.co/ Swipefile reference: https://swipefile.design/ref/lusion-webgl-world/ Captured: 2026-09-05. This is a dated reference, not a claim about the current live product. ## 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: Technically flexing but commercially serious. Opens with a trick to prove capability, then gets straight to the work. Reads as a studio that ships, not an experiment. - colors: Bright near-white paper for the content stretch, hard cut to true black for the WebGL beats. The 3D scenes carry saturated candy colour (electric blue, iridescent pinks) that never appears in the UI itself. - typography: Large tight-tracked geometric sans for statements, ~11px uppercase mono for project meta. Statements sit centred on their own screen with nothing else on it. - layout: Alternating full-bleed 3D beats and conventional two-column content. The grid is a plain two-up of project cards — deliberately unremarkable, because it is the part that has to be readable. - motion: Physics rather than a camera path: objects collide, tumble and settle under simulated forces, and the cursor pushes them. Scroll advances between beats while a decorative curve threads continuously behind the content. - texture: Matcap and clearcoat plastics, soft studio lighting, real contact shadows, subtle bloom. Surfaces read as injection-moulded objects photographed in a studio. - dont: Don't run 3D under the case-study grid. The whole structure works because the effects stop when there is something to actually read, and start again when there isn't. ## 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.

Copy promptDownload .md

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