A complex FileMaker solution may end up with many hundreds of scripts. Without any type of system for naming, the utility of being able to successfully use the Manage Scripts filtering feature becomes less useful - both for yourself and any other developer.
As a best practice, it is suggested that you choose predefined prefixes to identify certain scripts which perform known actions or have fixed associations. Using the colon (:) is what identifies the prefix from the name of the script. These should be documented in your default scripts where documentation is maintained.
The following present some useful examples. Using the prefixes of Button:, Create: and Delete:
New Customer vs. Button: New Customer
Create: New Customer vs. New Customer
Delete: Customer vs. Delete Customer
RowClick: Sidebar Select Customer vs. Select Customer
In the above examples, the keywords have been used to identify specific associations. Using the filtering field at the top of the Manage Scripts dialog means you can quickly find all scripts which are associated to "Buttons:". You should also note that there is a distinction between Button: New Customer and Create: New Customer where the button script is clearly associated to the button within the user interface (the layout), and the Create: New Customer is a general routine which is called not only by the Button: New Customer but also by any other script which may require the action of making a new customer.
Currently this page does not have a fixed list of suggestions for prefix names. It would be nice to have the community contribute to this. I've personally only used the few above.
Button: for any general buttons
RowClick: (special type of button) for any script tied to a portal row selection
ListClick: (special type of button) for any script tied to a list row selection
Create: for any script which creates a record
Delete: for any script which deletes a record