spackle

Overview

Every new project starts with the same setup: the folder structure, the configuration files, the boilerplate filled in with the project’s name and details, and a handful of commands to get it running. Done by hand, it’s slow, and no two projects end up quite the same. spackle turns that setup into a template. A configuration file declares the inputs a project needs, each with a type, a description, and a default, and spackle fills them into the project’s files. Hooks then finish the job, such as initializing a Git repository, and can be made optional or tied to specific inputs. Because each template describes its own inputs, spackle can check a template for problems and tell any interface exactly what to ask for.