Mahayana sees itself as going beyond what they might call "individual" or "personal" liberation, in that it sets up a grand goal of liberating all beings. Practitioners hold this ambition in mind, and see the "Hinayana" (small vehicle; a pejorative term used in Mahayana rhetoric to denounce other interpretations of Buddhism) ambition as limited or as merely a first step towards the ultimate goal of universal liberation.
How this relates to the Haskell prelude, I'm not so sure... but yeah, I suppose a "Mahayana prelude" is more grandly ambitious and therefore also more expansive and difficult to realize...
(By the way, in religious studies, Rupert Gethin's book The Foundations of Buddhism has an introductory chapter about Mahayana, and an in depth review is Paul Williams's Mahayana Buddhism: the Doctrinal Foundations.)
In practical terms a "big-vehicle Prelude" is saying "I want to do something much smarter than the original Prelude and I am willing to replace most of the underlying abstractions in the Prelude to do it," which can sometimes mess with code that has to deal with old-prelude and new-prelude subsystems of code. A "small-vehicle Prelude" is much more "I have a couple extra modules here and there that I want to import, and maybe I want to fix a couple of these operators to a slightly more general definition with a typeclass, but largely I want everything to be the same, hence intercompatible with minimum fuss."
"Big Vehicle Prelude - Fix most of the deficiencies in the Prelude by introducing new abstractions that replace large portions of the basic types and class, and generally redefine the way we write Haskell. See numeric-prelude.
Small Vehicle Prelude - Fix the broken parts of the Prelude by building on existing types and classes and masking broken bits. See basic-prelude."