Any errors here affect navigation and completion.

It is difficult to see what patterns are checked. We need a better way to describe them.

• build the patterns by scanning textual descriptions?
• use some kind of DSL?

In reality, doing this kind of scanning will always be prone to errors -- the right way is by parsing the code, but how do we do it for code that is in the process of being written/modified?