...

• AccountAfterUpdate-IsActive

• CaseBeforeUpdate-IsClosed

• OpportunityBeforeUpdate-IsWon

Person Accounts

Person Accounts are generally very separate to actual Accounts so I would always keep all flows separate. However you can’t do criteria at the Flow level for Before Create (obviously). So stick a decision node as the first element and check for Person Account (it knows it by then because you have selected a Record Type). Even if you then do nothing with the regular Account and name this AccountBeforeCreate-PersonAccount then it’s still better for long term maintenance. Also name all Flows with the words PersonAccount so you can filter on Person Account related Flows.

Rarely Used Fields

If a field is rarely used or just used once as a set and forget (toggle) type field, then any field updates that happen when this field is set can just go in another Flow. Then they don’t clog up the main Flows that need to be modified more often.

...