One of the most important aspects of maintainable code is readability. Being able to identify what something does just by reading the name. This applies to files, type names, functions / methods - all the way through.
You should not use abbreviations, unless they are well known and understood abbreviations,
JSON or similar.
Typically when working on features, the feature represents an artifact in the system. This artifact is often represented as a noun in the system and the feature concerning the noun should be pluralized.
An example would be for instance
Employee and the feature with everything related to
this artifact would be
Employees. Examples from our own code-base could be the
namespace, which holds Application.
Database schemas, folders in systems or in general collections of artifacts should similarly be named like this consistently.
Having prefixes or postfixes to type names is often considered a code-smell. It can be an indication that the name alone is not saying what it is actually doing. There is no reason to add the technical concern as a pre-/postfix. Examples of pre-/postfixes you should avoid:
Another common thing seen and done is to include the word
Base as a prefix or postfix.
This should not be there.
Instead of adding post/pre-fixes; make the naming unambiguous instead.