Folksonomy /fəʊkˈsɒnəmi/ (noun)
a user-generated system of classifying and organizing online content into different categories by the use of metadata such as electronic tags.

This in my opinion is one the best if not the best way to organize Figma files, no matter the size of the team. Most users are used to using folders to organize their files whether in Figma or their computer and this is to the fault of how computer file structures were designed. Folksonomy or the use of metadata such as tags for classifying and organizing files is significantly more scalable and powerful. I do think Figma needs to speed up the way they handle queries and their search feature. But assuming everything works smoothly, this could be a game changer.

Personally, I have lots of use cases for tags in my Figma design files. We use a versioning system at my company for design files, this is so our different departments such as product and engineering can be working on different versions at the same time. This not something “branching” would solve, as we would need multiple versions available and the ability to return to previous versions at anytime, it needs to be super simple. We currently use the pages in design files for this.

Adding a tag for each version a design file has would be incredible, it would make it a lot easier for all teams to just find every design file that’s part of a specific versions. For context, versions are created per sprint. This means we don’t version per file, but per sprint. So if a sprint is version 4.20, you can search all files that have been updated for that 4.20 sprint if we had tags.

P.S the original post is clearly a feature request, not a question. It should be categorized and treated as such.