Another option for distinguishing features from other `@type`s is to make them a string instead of a keyword. Then, they could be used as above (`.note@{kind} { ... }`) and can still be matched differently.

Normally we'd match using the string itself (ie `.mixin(@part; 'howto') { ... }` but for the autogenerating skeleton code we could match any feature by using `.mixin(@part; @context1; @contexts...) when (isstring(@context1)) { ... }`

(I may need a better example)