Mostly I took examples from https://www.dofactory.com/ and "https://en.wikipedia.org
Sometimes I edited them for greater clarity from my point of view.

I add the interesting pattern to the OtherPatterns dir.

Behavioral

1. Strategy** is just implements the meaning of an abstract class or interface and nothing more.

2. Template is often used, natural as a strategy pattern. One of the implemented methods calls several abstract methods. Similar to a factory.

3. Visitor is nice pattern, I would call it as a combinator or a Heir, something like that.

4. ChainofResponsibility, in general, the pattern, judging by the name, is obvious and in demand: each actor has, or at least needs, one to whom a task can be delegated. Class "A" has a "next" property of type "B". "A" and "B" implements the same interface, so you can chain A.next=>B.next=>C.next Thus, the process of coordinating documents always goes on. First, the document gets on the table to the secretary or the first person, which structures are determined, the chiefs of lower rank must agree on it and in what sequence. If "next" is not set, this is a case when the task is outside of competence of the current actor, and it is not possible to delegate it to someone yet, then an error is thrown. But still, the pattern is a little far-fetched. Any programming usually consists of chains of calls like A.method1 => B.method2=>C.method3. If the names of the methods are the same, nothing changes dramatically.

5. Command is a pattern that is useful when you want to keep the ability to execute "undo/rollback" and "redo" operations. The information about the performed operations is stored in an array. The calculator is a very good example for such behaviour.

6. Interpreter looks like a factory. The product goes through sequential processing. Similar to the chainofResponsibility pattern. They are interchangeable.

7. Iterator is Enumeration, not significant.

8. Mediator. The chat participant calls the Chat.Send command. The chat stores information in the participant class.

9. Memento saves a state of the class. The trick is that the class that serves to save the Memento state is encapsulated, is private.

10. State allows an object to alter its behavior when its internal state changes. The state pattern can be interpreted as a strategy pattern, which is able to switch a strategy. The state pattern is used in computer programming to encapsulate varying behavior for the same object, based on its internal state. This can be a cleaner way for an object to change its behavior at runtime without resorting to conditional statements and thus improve maintainability.

11. Observer is a good patterп.

Structural

1. Adapter Is it possible to convert one type to another without using adapter?
2. Bridge is fine pattern. People have similar roles, but depending on their nature, everyone performs them differently.
3. Composite
4. Decorator
5. Facade is about how an usual service workflow probably looks like: checking counterparties, processing requests, parsing, logging, recording in database.
6. FlyWeight
7. Proxy It's probably used. In principle it is logical.

Creational

1. Abstract is often used
2. Builder actions are defined by the interface.
3. Factory is a similar template.
4. LazyInitialization is a lazy class.
5. ObjectPool
6. Prototype creates a class by cloning.
7. Singleton is oftet used. Its disadvanges is that it complicates testing process.
8. MultiTon is the several singleton, it complicates testing too.
9. ResourceAcquisition

By and large any programmer who uses interfaces and abstract classes codes with patterns in any way. There is no another choice.

As a joke, I present excerpts from 2 books.

The Twelve Chairs by Ilf and Petrov

On the third move it turned out that the grandmaster was playing eighteen Spanish games. In the remaining twelve, Black used the outdated, but quite correct Philidor Defense. If Ostap had learned that he was playing such tricky games and facing such a proven defense, he would have been extremely surprised. The fact is that the great schemer played chess for the second time in his life.

THE MIDDLE CLASS GENTLEMAN(Le Bourgeois Gentilhomme) By MOLIÈRE

MONSIEUR JOURDAIN: Please do. But now, I must confide in you.
I'm in love with a lady of great quality, and I wish that you would help me write something to her in a little note that I will let fall at her feet.
PHILOSOPHY MASTER: Very well.
MONSIEUR JOURDAIN: That will be gallant, yes?
PHILOSOPHY MASTER: Without doubt. Is it verse that you wish to write her?
MONSIEUR JOURDAIN: No, no. No verse.
PHILOSOPHY MASTER: Do you want only prose?
MONSIEUR JOURDAIN: No, I don't want either prose or verse.
PHILOSOPHY MASTER: It must be one or the other.
MONSIEUR JOURDAIN: Why?
PHILOSOPHY MASTER: Because, sir, there is no other way to express oneself than with prose or verse.
MONSIEUR JOURDAIN: There is nothing but prose or verse?
PHILOSOPHY MASTER: No, sir, everything that is not prose is verse, and everything that is not verse is prose.
MONSIEUR JOURDAIN: And when one speaks, what is that then?
PHILOSOPHY MASTER: Prose.
MONSIEUR JOURDAIN: What! When I say, "Nicole, bring me my slippers, and give me my nightcap," that's prose?
PHILOSOPHY MASTER: Yes, Sir.
MONSIEUR JOURDAIN: By my faith! For more than forty years I have been speaking prose without knowing anything about it, and I am much obliged to you for having taught me that.