Loading video...

Video Failed to Load

Go Home

Directional Jump Pads added ‼️ Useful for practicing send lineups 😁 map code: 3249-8633-5606

44,773 views • 1 year ago •via X (Twitter)

10 Comments

aviate amadeus's profile picture
aviate amadeus1 year ago

@ohfraser @obeykenzi

kurt's profile picture
kurt1 year ago

Greatest sender of all time

Severe's profile picture
Severe1 year ago

goat

Seany's profile picture
Seany1 year ago

🫡

Eskae's profile picture
Eskae1 year ago

change the blue launchpad to the purple one already

Seany's profile picture
Seany1 year ago

Unfortunately uefn doesn’t have the purple launch pad /:

jordan's profile picture
jordan1 year ago

@makowyddd the bandi to jump pad

bibou😸🎈's profile picture
bibou😸🎈1 year ago

These are in creative 1.0?

Seany's profile picture
Seany1 year ago

No they are artificially made by me 😄 took me hours

Bubble's profile picture
Bubble1 year ago

fantastic

Related Videos

THIS GUY BUILT A CLAUDE CODE X OBSIDIAN MAP OF HIS ENTIRE CONTENT SYSTEM This is the useful version of “AI second brain.” Not dumping more notes. Not asking Claude for a prettier folder system. Not making a canvas because it looks smart. In the video, he points Claude Code at his Obsidian setup and shows a visual map of the actual content pipeline: Analysis Ideation Prep Scripting Prep Performance The interesting part is the shape. Each stage is connected to the next one. Some boxes show sub-processes. One section shows a router detecting content type and routing a short into the next step. There are references attached to the flow. That is a real payoff: you stop treating your vault like storage and start treating it like an inspectable machine. The move is simple: 1. Put the real workflow in markdown 2. Let Claude Code inspect the vault 3. Ask it to find stages, dependencies, and missing links 4. Turn the output into an Obsidian map 5. Use the map to see what is manual, duplicated, or broken This works because Claude Code is not just summarizing a note. It can read across prompts, docs, scripts, references, and messy process files, then expose the structure you stopped seeing. That is why the demo hits. The video is not really about “better note-taking.” It is about making your private operating system visible enough to debug. Caveat: a beautiful graph does not mean you have a working system. If the notes are vague, the map will be vague. If the process is fake, Claude will draw a fake process very cleanly. If nothing feeds back into performance, the canvas is just decoration. But if the vault already contains real work, Claude Code x Obsidian becomes a powerful audit tool. Your notes stop being a pile. They become a map of what you actually do.

kocer

15,941 views • 2 months ago