WSL is useful when I need Linux tools while working on Windows. I want to be clear about where the editor, terminal and project run. Mixing Windows tools and Linux-side dependencies for the same project can make paths and setup confusing.
What I like about tmux is being able to name sessions. A project's server and shell can stay together in one session. When I come back from something else, it's easier to tell what each window is for.
To return to a session called website, for example:
tmux attach-session -t website
I use Starship for the prompt. The directory and Git status are enough for me, and I can change the appearance in its configuration file. Tools like zoxide are useful for reaching directories I visit often.
I don't think a terminal setup needs every one of these tools. I'd start with a plain terminal and notice which actions I keep repeating, then add something that helps with those.
Starting a session
Inside the WSL terminal, I create a named tmux session:
tmux new-session -s website
I'm now inside tmux. I can enter the project directory and start its server here. Ctrl+b, then c creates another window. The server can stay in the first while I use Git in the second. Ctrl+b, then n moves to the next window.
To detach, press Ctrl+b, then d. That leaves the tmux session running. Later, tmux attach-session -t website reconnects to it. tmux list-sessions shows the available sessions.
This lasts while the tmux server is running. I don't expect processes to survive shutting down the computer or WSL. The tmux getting-started guide is a useful reference for the commands and shortcuts.