If you use the instance name method, then the headers in the option and attribute change with the instance name, so no point in being specific when creating the DCs. So start with one simple rectangular solid, add the attributes commonly used and any for the reports, avoid using the Name attribute as this will override the instance name. For this template DC, you need to saveas then bring it back into a new or purged of this DC file, this will activate the connection between the DC and instance names. Then you can create a range of basic DCs using this template, via right click menu, making unique and scaling definition if required then saveas to a folder. For any child component or group after creating them, change their reference to their parents title to the generic, that is …
myDCparent_somename!an_attribute
to
parent!an_attribute
then you can change the instance name without effecting the formula
see a file with more detail, the parts are all generated from the simple one, then put together to create the object, this is saveas and brought back in to a clean working environment to activates its instance connection
Axis to a certain degree is important, I first started follow the Sketchup using Y as my length with x-z as the profile, now because of materials I am converting to Z, so grain flows in the Z direction or you could use the X, either way you would create your material folders based on the choice.
The x/y is always the gluing and cutting face.
At this point, as the position and rotation of components is somewhat fiddly, you should consider using scripts, like one that accesses your folders, and places the component within two or more points, scaled and rotated in one action, Such script would be personal to your DC sets. For this, the axis and insert point for the parents would all be the same.
Other scripts could freeze and simplify the heavy DCs somewhat like the new Live components (although this concept predates them) reactivation is simply done by swapping the instance with the folder saved version of the DC.
Swapping DCs with other DCs and connecting similar attribute values is done by using the Current formula and having a lower nesting read the values. (an extra level, a good point in the simplification, or where formula is kept leaving the parent to collect data)
I use simple attributes relevant to the context, specific attributes to report data and use the a,aa ab, just in the parent to organise the positions in the option dialog