[Question/Feedback]: A specs for coding guidelines (SHOULD)

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Description

For example
- You shall use ShallowMerge() over Union() if you are conditionally not allowed to provide a property in a properties block (as opposed to providing empty/null)
- You shall not pass defaults into child modules if they already have defaults defined
- You shall put the import statement of a type on top of a parameter's description not below, as it will otherwise mess up your template
- ...

No file, test, or entry point is named. Start by reviewing the existing issue discussion and the repository’s module standards, then define the scope of the proposed SHOULD guidelines. Done means an agreed specification documents rules such as ShallowMerge() versus Union(), child-module defaults, and import placement.

Written by the indexing model from the issue text.