https://www.red-gate.com/simple-talk/blogs/sql-naming-conventions/
It helps greatly to start with a dictionary of the correct nouns and verbs associated with the application domain and use that.
If it proves inadequate, then the team can build on it.
If a data model has been created as part of the design phase, this dictionary should be an end-product of this work.
Don't tibble, no tbl_ or rpt_
Avoid, where possible, concatenating two table names together to create the name of a relationship table when there is already a word in the language to describe the relationship. e.g. use Client rather than EmployeeCustomer
https://steelkiwi.medium.com/best-practices-working-with-django-models-in-python-b17d98ab92b
https://books.agiliq.com/projects/django-orm-cookbook/en/latest/table_name.html