Before you can follow Kruskal or Prim, you must be able to look at a symbol like (w,u,v), or the phrase "same component", or O(ElogV), and instantly picture what it means. This page builds every one of those from nothing, in an order where each idea leans on the one before it.
The whole set of vertices is written V. When we say "there are V vertices" we are (slightly loosely) using the same letter V for both the set and its size (how many dots there are).
WHY the topic needs it: an MST must "touch every vertex". If you cannot picture a vertex as a dot, the phrase "touch every dot exactly once" has nothing to hold onto.
WHY the topic needs it: the parent note's biggest "steel-manned error" is thinking MSTs work on directed graphs. They do not. The very definition of MST assumes every edge is two-way. If edges had arrows, "connecting two islands" would become ambiguous — which direction? So we insist on undirected from the start. (The directed cousin is a different beast, stored differently too.)
WHY the topic needs it: an MST only exists if the graph is connected. If two clumps of islands have no bridge between them at all, no set of edges can ever join them, so "spanning" everything is impossible.
WHY the topic needs it: this is the heartbeat of Kruskal. Every time Kruskal considers an edge (u,v) it asks "are u and v already in the same component?" If yes, connecting them again just makes a loop — skip it. That single question is answered by Disjoint Set Union (Union-Find).
WHY the topic needs it: the parent's entire correctness proof rides on the cut property — the cheapest crossing edge of any cut is safe to add. You cannot read that theorem until "cut", "V∖S", and "crossing edge" are pictures, not symbols.
α(V) — the inverse Ackermann function. Grows so unimaginably slowly it is effectively constant (≤4 for any graph in the universe). It measures the cost of one Union-Find operation.
A min-heap / priority queue — a data structure that always hands you its smallest element fast. This is Prim's engine; details in Priority Queue (Binary Heap).
Prim's heap skeleton is identical to Dijkstra's Algorithm — the only difference is what number you store as the key (edge weight vs. path distance).