Sometimes patters are prose about arrangement, sometimes template can be provided and in some cases even fully functional, generic code can be provided.
I don't see anything wrong with calling them "design patterns", software is about "designing" systems and "pattern" reflects the fact that they re-occur, can be reused, can be applied to similar problems etc.
The value is in recognising similar structures, communicating them, reusing solutions to already thought through problems etc.
Poorly designed code can be recognised straight away with ad-hoc, incoherent spaghetti. On the other side there are many poorly applied "pattern" implementations with idiotic verbosity that should be called out as "anti-patterns" instead (just mere change of the language is enough to move a pattern to anti-pattern).
Just because it can describe about anything doesn't make it pointless, just like "best practices" section can be about anything, it doesn't mean it makes it pointless.
Anti-patterns are very useful concept as well.