Many choose to fail forward instead. If something is broken, fix it with a new migration (not by rolling back a previous one).
I've found
down() occasionally useful in localdev while working on a feature, because it's faster than a php artisan migrate:fresh --seed, but I've…it's optional, but rolling back without it gets you "table already exists" on the next migrate 😅