IMO, a good topic order for these slides might be:

1. match syntax overview
2. Literal constant patterns (i.e., "Primitive Patterns")
3. Reference patterns (variable references and member references)
4. Object patterns
5. Array patterns
6. Discards/void patterns
7. Extractors
8. Combinator patterns (and/or/not/parens)
9. Variable declaration patterns (i.e., let/const/var) - calling them "Binding Patterns" is mildly confusing as JS already has something else called a binding pattern
10. if patterns
11. Semantics of custom matchers
12. Future syntax

This order progressively builds in complexity while leveraging key information from previous slides. For example if patterns really need and to be meaningful. Oftentimes, so do let patterns.

Also, as mentioned above, in slide 19 "Extractor Patterns", true is not the same as []. Honestly I'd rather a custom matcher throw if you use it as an extractor and it wasn't written to be used in that fashion.

We may also want to describe or, and, and not as "Disjunction", "Conjunction", and "Negation" patterns, but that's my personal preference.

pattern `{ a }` is already an early error in the spec due to the possible confusion. https://tc39.es/proposal-pattern-matching/#sec-match-patterns-static-semantics-early-errors