Once your library reaches a certain size then you start needing codewords to jump to the specific sounds you're looking for quickly. This is especially true with common sounds like impacts, whooshes and UI.
For example, I have a batch of custom UI servo digital sounds that I tag with the word "clix" on them, because I know that if I just search that term nothing else in any of the purchased libraries will show up.
I also have a huge batch of custom impacts that we call "etolls" here because the first batch was inspired by a Robert Etoll library that a director brought into the facility. The library left with the director when the project was finished, but the sounds inspired me to make some of my own. At this point I've built hundreds of our own custom "etolls", and everyone in the facility uses that specific search term to find those specific sounds. (I should change them to Coronados, but that'd throw everyone off) :)
The other helpful thing is that soundminer includes file structure in the search, so I can look for "dapg amb" and get all of the custom ambiances I've recorded here at Dallas Audio Post Group - since all of our custom stuff lives in its own master "DAPG" folder.
I also tend to tag these boutique libraries so that I can find them quickly. I know exactly what I'll get if I look for a "tim seal" or a "rabbit rocket"
So, do you use specific code words to isolate the cream from the rest of the crop when doing sfx searches? What kinds of words do you use?