But the answer is in your own sig
It's a rainy coastal day here so I'm reading up on extended chords, much of that is UFN as it were in my project. But there are already three settled issues if for no other reason than the fact that a slash cannot be in a file-name.
The "Add" invention is nice but it takes up 3 characters whereas the ideal symbol + is only one. If the + sign was deployed to indicate 'augmented' that was a monumentally bad choice, sooner than later someone' going to correct the mistake anyway so for my own use that's going to be now.
Similarly the chord file-name has to reveal as much as possible because every diagram HAS to have a unique name. Every chord that sounds different in any way IS a different chord even if it's been called by the same name and every different chord must have a diagram of it's own. It's a can of worms that could easily be fixed with 30 character long file names but those would then be unusable in human terms. Stuffing string and fret #'s into it gives a more unique file-name without going overboard.
But problems arise enroute. Take for example these C chords with tentative provisional file-names
a basic C triad 1st inversion
the same basic C triad with an extra 1st in the bottom making it lean toward the same file-name because it's also a 1st inversion with the root on the #01 string at the 10th fret but I cannot have duplicate file-names so interim I gave it a -L1
but if I reconfigure the above (conceptually only because it's still the same chord) to do away with the inversion then the root goes to string #04 at fret #0 i.e. open-string giving me a different file-name. This is the kind of problem I have to work around in many different situations. The likely outcome of the above will be that I simply kill the -L1 version which is in name only anyway and keep the other two.