# Animated UMAP explainer for undergraduates

> A 5-minute narrated explainer on how UMAP works: nearest-neighbor graphs, fuzzy weights, layout by attraction and repulsion, and how to read the plots. Claude Opus 5.5 wrote the narration and designed the visuals, prompted from Claude Code on a phone.

- Kind: Video
- Page: https://meetreference.com/v/animated-umap-explainer-undergraduates/
- Ready-to-use agent handoff: https://meetreference.com/v/animated-umap-explainer-undergraduates/agent.txt
- Authorship: AI-made, per the source
- Made with: Claude Code
- Model: Claude Opus 5.5
- Built with: not stated
- Style: Math & science; narrated, explainer, machine learning, animated diagrams, dark, point clouds, square
- Length and format: 5 min, 1:1 (720x720 source)
- Shared by @goodside in X, Sep 25, 2026: https://x.com/goodside/status/2103505085292593220
- 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 video

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

Teach an algorithm in numbered chapters on a near-black field, each opened by a small orange chapter label and one plain heading. Build every idea from custom point clouds and graphs: teal edges for neighbor links, distinct colors for clusters, yellow rings on the points being discussed. Use side-by-side panels for comparisons and labeled sliders for parameters, and close on a four-panel recap. For a new subject, keep the chapter structure and replace the diagrams with your own data.

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 video frames, not by the creator.

A dark, diagram-led lecture on UMAP in numbered chapters, built from point clouds, neighbor graphs and small labeled panels.

- Color: Near-black background, white headings, grey points, teal-green graph edges, blue and orange for dense and sparse points, multicolored clusters, and yellow rings and sliders.
- Type: Bold sans headings at the top left ("Nearest neighbors", "Pull and push", "The two knobs"), small orange-dot chapter labels such as "3 · STAGE 1 · BUILD THE GRAPH", and monospace for parameters and values.
- Framing: Square frames with the heading at the top left and one large diagram below; comparisons sit in rounded panels, and a thin progress bar runs along the bottom edge.
- Structure: 70,000 handwritten digits as the hook, the problem of unrolling a curled sheet, building the neighbor graph and a per-point ruler, where layout starts and pull-and-push, the two parameters on a mammoth point cloud, how to read a UMAP plot, and a four-panel recap.

Storyboard, nine frames spread across the video: https://meetreference.com/media/animated-umap-explainer-undergraduates/storyboard.webp

- Frame 1 at 17.0s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f1.webp
- Frame 2 at 50.9s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f2.webp
- Frame 3 at 84.9s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f3.webp
- Frame 4 at 118.8s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f4.webp
- Frame 5 at 152.8s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f5.webp
- Frame 6 at 186.7s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f6.webp
- Frame 7 at 220.7s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f7.webp
- Frame 8 at 254.6s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f8.webp
- Frame 9 at 288.6s: https://meetreference.com/media/animated-umap-explainer-undergraduates/f9.webp

## How it was made, per the creator

- Notes: In a reply the creator says it took a few rounds of planning and outlining at medium effort, then one prompt at Extra effort to make the video. The prompts are in a shared Claude Code session that needs a claude.ai sign-in, so Reference has not copied them.

> All of this—the concepts for the visuals, the narration, etc.—is from Claude. Prompted in Claude Code on my phone.
> (@goodside)

## Links

- Watch: https://x.com/goodside/status/2103505085292593220
- Original post: https://x.com/goodside/status/2103505085292593220
- Claude Code session (sign-in needed): https://claude.ai/code/session_01EDqKuj1DA5BK6LJxMYGvZZ