Looking through the Drupal coding conventions on Coding standards / Naming Conventions, I have seen module, variable, function, and many other areas but not for permission names.
Is there any convention to avoid creating permission names that might interfere with others?
AFAIK there's no official recommendations.
Given that all permissions share the same namespace it's a good idea to avoid generic names. You can include the name of the module that defines the permissions to minimize collision risk.
The Drupal coding standards do not say how permissions should be named, especially to avoid collisions between permissions defined from different projects.
The permission names used by Drupal core follow the schema <verb> <object>, as administer users, view user email addresses, administer nodes, and administer content types.
Usually, <object> is derived from the module name, and that avoids conflicts, but that is not always true.
