# Interactive camera lens lab

> A three-dimensional optical workbench explains camera focus using an exploded lens, traced light rays, a movable focus plane, and a miniature mountain scene, with focus and aperture controls and comparative image previews.

- Kind: Interactive reference
- Live interactive reference: https://lens.lab.sael.net
- Page: https://meetreference.com/v/ref-interactive-camera-lens-lab/
- Ready-to-use agent handoff: https://meetreference.com/v/ref-interactive-camera-lens-lab/agent.txt
- Authorship: AI-made, per the source
- Made with: Not stated
- Model: Claude Opus 5.5
- Built with: not stated
- Style: Interactive explainers; optical visualization, exploded view, cinematic lighting, dark interface, scientific instrument, miniature diorama, glass materials
- Playback: a muted visual reference. The original soundtrack is available only at the source.
- Shared by @RyanSael in X, Sep 23, 2026: https://x.com/RyanSael/status/2102591147927654847
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this interactive reference

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Build the explanation around a tangible apparatus, exposing internal components and overlaying thin ray lines and a translucent gridded plane. Pair the main scene with compact numerical readouts and a strip of image comparisons so parameter changes have several visible consequences. Use close-up inspection views alongside the full assembly; for a new subject, replace the lens and landscape with the relevant mechanism and test specimen while preserving the connection between controls, internal behavior, and observable results.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the recording frames, not by the creator.

Dark, polished technical simulation with glowing glass and light-ray diagrams.

- Color: Deep navy and charcoal with cyan-blue highlights, white text, and warm amber accents.
- Type: Small, clean sans-serif interface labels and controls; legibility is secondary to the diagrams at this scale.
- Framing: A central horizontal lens apparatus anchors the overview screens, with control panels above and below; close-ups enlarge the lens and projected image.
- Structure: Dashboard-style interface with repeated overview views and detailed views of the lens, light path, and image plane.

Storyboard, nine frames spread across the recording: https://meetreference.com/media/ref-interactive-camera-lens-lab/storyboard.webp

- Frame 1 at 1.8s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f1.webp
- Frame 2 at 5.3s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f2.webp
- Frame 3 at 8.9s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f3.webp
- Frame 4 at 12.4s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f4.webp
- Frame 5 at 16.0s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f5.webp
- Frame 6 at 19.6s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f6.webp
- Frame 7 at 23.1s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f7.webp
- Frame 8 at 26.7s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f8.webp
- Frame 9 at 30.2s: https://meetreference.com/media/ref-interactive-camera-lens-lab/f9.webp

## How it was made, per the creator

- One-shot: yes, a single prompt with no follow-ups
- Agent time: 1 hour 26 minutes
- Reported spend: $25.66 API

## Links

- Open reference: https://lens.lab.sael.net
- Watch: https://x.com/RyanSael/status/2102591147927654847
- Original post: https://x.com/RyanSael/status/2102591147927654847