I noticed Jdlrobson poking around on enwiki starting to add support for dark mode in TemplateStyles. (And then fixed some things.) One of the qualities I definitely came to the conclusion though looking at the kinds of changes that need to be made is that the two classes currently indicating dark mode *of some kind* are terribly named for arbitrary users who may come later.
```
.skin-night-mode-clientpref-1
.skin-night-mode-clientpref-2
```
My principle concern was the `clientpref-n` which does not describe whatsoever for arbitrary user what the intent of these client preferences are. Right now, `clientpref-1` describes someone who has selected "dark mode" and `clientpref-2` describes someone who has selected "let the browser decide based on previous settings". Only by inspecting their uses rather than their names are their uses obvious. And moreover, it would be easy to typo them and drop people into darkness while in the light... or vice versa.
Separately, Jdlrobson noted there was some pain with the naming of `night mode`, and from my perspective I would definitely be concerned that this naming does not extend 'cleanly' to arbitrary other themes (such as the additional currently extent sepia in the app[s]).
# Acceptance criteria
[] The change should be done in a backwards compatible way
[] This should not impact the instrumentation.
# Sign off steps
[] Document the new classes on recommendations for night mode compatibility on Wikimedia wikis - MediaWikihttps://www.mediawiki.org/wiki/Recommendations_for_night_mode_compatibility_on_Wikimedia_wikis
[] Update the on-wiki references to the old classes (ask Jon to do this)