Absolutely #TDD supports good design!
I still see people saying TDD "forces" good design, or bad design (depending on their agenda), and I'm trying to push back against that.
It's a tool, that I find extremely helpful for adaptive and emergent design, but it's a tool that still requires some sense of what "good design" is.
I've done "good design" before I went 100% TDD, though I wouldn't do that again if I had a choice.
#TDD is a great tool for surfacing design issues, but if you can't see what it's showing you, or ignore it, then you might create "bad" designs.
At least you'll have tests for the code you have? But if you ignore coupling, then they may be overly tied to implementation, which will make refactoring difficult.