Smarter search: tag:, user:, and deck: prefixes
October 14, 2026
Search used to run one broad query over decks and hope the result was what you meant. Searching "spanish" could reasonably mean a deck named Spanish, a tag called spanish, or a user named spanish -- and you'd just get whatever the search happened to rank first.
The fix: say what you mean
Three prefixes now scope a search explicitly:
deck:spanish-- only decks named like "spanish"tag:spanish-- only decks tagged "spanish"user:spanish-- only user profiles matching "spanish"
The prefix is case-insensitive, so TAG:, Tag:, and tag: all work the same way.
Small details that matter
Typing just a bare prefix with nothing after it -- say, user: with nothing following the colon
-- isn't treated as an error or a broken query. It's treated as if you'd typed nothing at all,
since there's nothing meaningful to scope yet.
The empty-results message changes based on what you scoped to, instead of one generic "no
results" for everything: searching deck:zzz with nothing found tells you there's no deck named
that; tag:zzz tells you there's no matching tag. A small thing, but it means the empty state
actually answers the question you asked instead of leaving you guessing whether your search even
ran.