Role-model checklist . GitHub File Check with Rubrics - chatGPT.
Test your monolith or module's file and give it a score 1. Role-Model Source File Checklist (Yes / No) You can literally print this and go line by line. A. File Structure Does the file have a clear top-to-bottom order (for example: imports → constants → types → internal functions → exported functions)? Is everything in the file clearly part of a single module or concern? Is the file short enough that you can scroll through it without feeling lost (for example, roughly one screenful or a few screens, not hundreds of lines of unrelated stuff)? Are there no obvious “god functions” doing too many different jobs? B. Naming Do function names describe their purpose, not their implementation details? Do variable names reflect domain concepts instead of single letters (except for tiny scopes like loops)? Is naming consistent with the rest of the project (same terms for same concepts)? C. Interfaces and Behavior For each exported function or class, can you...