Alternative variable token (for use in package.json for example)

Nobody has claimed this yet.

I'm interested in adding an alternative variable token identifier to `create-project`: one that allows me to add variables to package.json's `name` field, in a way that doesn't cause npm to fail an `npm install` step inside a template repo.

Need to research how I could do this still, but basically in addition to `{{ variable }}`, there could be some other identifier that doesn't make npm mad e.g. (`cpt--variable--cpt`) or something.

The goal is that a template repo can install dependencies and run scripts.

I would be willing to implement and submit if you are willing to merge.

Start at the create-project variable-token handling and investigate how package.json name values interact with npm install in a generated template repository. Define an alternative token alongside {{ variable }} without causing npm validation failures. Done means a template repository can install dependencies and run its scripts successfully with the substituted package.json name.

Written by the indexing model from the issue text.