The naming style itself, whether camelCase or with prefixes or whatever convention you prefer, matters far less than the simple fact of giving it a meaningful name in the first place. A Flow full of elements called "Get_Records_2" or "Assignment1" tells you nothing six months later when you're trying to debug it, while "Get_Open_Opportunities_For_Account" tells the whole story at a glance.
Try to follow one convention, at least within a Flow.
Book a free 60-minute Salesforce Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.