Naming convention for FileMaker code objects - touched by an external technology?

In determining a naming convention for FileMaker code objects including Let Variables, Custom Functions, FieldNames, etc., I think about whether a FileMaker code objects is currently, or might in the future, be touched by an external technology that treats characters, for example, ~ in ways that would break an integration.

Let Variables and Custom Functions do not seem to be currently, nor likely in the future, to be touched by an external technology. This offers an opportunity to employ characters unique to the names of those code objects, for example @my_custom_function, to make code more readable and searchable.

The _ character, while safe, seems to be over utilized in filemaker code. Other chars should be giving a chance to stand out!

Thoughts?

Riffing off a good Tweet...