Why do you call them design playgrounds?
Mostly because I didn't invent the term. If you've been a front end developer, a playground is a familiar concept: a tool that lets you manipulate variables and see their outcomes on an interface in real time. I just borrowed it for designers who are now building these tools for themselves.
The name also fits how you use one. You can see a bunch of variants at once (long text, short text, no text), play with options (big text, bold text, red text), and actually interact with designs. That's a lot closer to messing around on a jungle gym than carefully pushing pixels in a mockup. The agent work demo I mentioned earlier is a good example. I built it to try out different ways of showing an agent's work, tweak details, and animate them to see what works best.
And then there's the disposable part. Building playgrounds used to take more time than they were worth, since you'd probably never use the tool again. Now a frontier model with a good harness can whip one up in minutes at minuscule cost, so you can spin up a playground for a single design question and toss it once you've got your answer.
So the name sums up the attitude: design tools used to be something you spent years learning, and now they can be something you make, use for an afternoon, and happily move on from. You go to a playground to play, and then you go home.