Do rigid design systems kill creative problem solving for developers?

Having a solid component library saves a ton of time but sometimes it feels like it takes away the freedom to actually think about what a specific screen needs. You end up trying to cram a unique feature into an old component box because "that's how we always do it.

" Products usually feel much better when the core experience stays coherent but individual screens are allowed to solve their specific problems naturally.

Do you prefer strict design guidelines, or do you give your team the freedom to invent new patterns when needed?