I've been putting together a cookiecutter repo to migrate Rainmeter skin development to github quickly & easily. Here's my idea of what the process should include:
Ask for project/repository name. This will be applied to repo-name as a slug & (if creating a new skin) the skin's root config folder & file names
Ask for user's full human name (gets applied to RMSKIN.ini, license, and metadata->Author field on a new skin)
Ask for user's github account username (required for templating status badges on README)
Ask for required Rainmeter Version (gets applied to RMSKIN.ini, defaults to currently installed version)
Ask for project short description (applied to README & metadata->Information field on a new skin)
Pick from a list of installed skins to import (only 1 allowed for initiatization) or create a blank skin (default option)
Ask user to pick a license (initial offerings are those suggested on Rainmeter Docs, but can be modified after cookiecutter finishes)
To do this I've written a python script that wraps the python module, cookiecutter. This script is needed to read some data from the system to suggest for default inputs (value used if user just pressed "ENTER" without inputting anything) before offering the cookiecutter options to the user. These data include: currently installed Rainmeter Version, Rainmeter's Skins Path (& a list of currently installed skins), the current year (for licenses where applicable). Depending on the user's choice about importing an installed skin, a pre-generation script will do some extra work to import the skin and ignore the included template skin or vice versa.
Thoughts going forward:
Should we make considerations for the @Vault folder?
Should we let user specify version of windows required?
What about skin documentation (other than just a readme)?