Which shortcuts should be in our library and which not?

[Steffen]

I agree with Chris and Santeri.
The misuse of the Shortcut is widespread.

Adding two parts in a shortcut, like a rim+tyre, is not a difficult assembly that should be handled in the library.
OTOH, there is a need to show what tyre and rim that fit together. But should we really create a bunch of shortcuts
everytime a new tyre is release by LEGO?
We have a number of, IMHO, usless shortcuts. Whats the point of having a compressed shock absorber in the library?
Why should we have shortcuts to easy the use of parts in a specific software? What is the difference between a
shortcut and a templete?

This assembly is a good one to have. The correct positioning of a rider on the scooter is not easy.

I think we need something like this:
Templete.
Shortcut.
Part assembly.
But how are they defined?

The Minifig Chain 6L is another good example.
One file is a formed chain to be used in as a shortcut, in a model, exactly 6L long.
The other is a straght chain extended to is maximum length, to be used in a build instruction.
I see no reason to shorten the 16/17 long chains, unless the chain is given a caternary shape.