So thinking more about this more, I could imagine a user experience
User adds some basic information about the style (field, type, etc.)
Wizard uses that information to present user with a handful of
previewed choices; user chooses closest match.
The “closest match” view allows users to choose among a few more
Upon choosing that match, user can either keep things as is and
proceed to saving the style (in which case the style is likely to be a
dependent style), or choose to “edit” it, which would present the UI
Dan is talking about. That way, the hairy stuff like names and dates
and macro order are likely to be correctly configured, so that the
user is only tweaking things like punctuation.
In any case, a lot of options here. The key decision is whether we
start with the macro-based approach.