Lately the idea of a "specialist" (at least in webdev) has come to mean (in my head): "I really know how to use this particular framework, but do not understand any of the surrounding technology. If I reach a problem, I will bloat the code with more libraries until it starts to work."
When people ask what are my particular areas, I'll say I mainly do... I'm expert in... I have strong experience with... over the years I've worked in several technical areas...
And list 4 or 5 different specialisms where I would realistically do ok if interviewed in those areas on the spot without warning.
I don't know if that would work for someone who really is a generalist without specialist knowledge at the current stage in their career.
In my case, I really have gone much deeper than most people into a number of different sounding domains. Not different skills or tech stacks, but really very different tech areas. I'm often regarded as interesting because of that, rather than "master of none".
But true, normally interviewers already get confused when you mention a skill that is not directly required by the job ad.
https://en.wikipedia.org/wiki/Jack_of_all_trades,_master_of_...