prj-creator is a Python CLI tool for scaffolding numbered project folders with optional templates for web, firmware, Python, docs, tests, and Git setup.
- Creates a new project folder using the next available number, for example
01.my-project,02.another-project - Lets you choose a setup style from the interactive wizard
- Generates common starter files such as
index.html,style.css,main.js,.env.example, andblueprint.json - Can create a Python virtual environment
- Can initialize Git, set
mainas the branch, commit the project, and push to one or more remotes - Can download template folders from a GitHub repository
- Bundled starter templates include
basic-web,npm-package, andpython-pypi
Install from Python packaging:
pip install prj-creatorIf you want to work from source, install the dependencies listed in src/pyproject.toml:
pip install requests InquirerPy colorama rich GitPythonprj-creatorThe tool supports one command-line option for loading an external template source:
prj-creator --command source:https://github.com/user/repo-c,--command: load templates from an external GitHub repository insource:https://...form
When you run the CLI normally, you will be asked to choose one of these modes:
Manual Setup: choose features like web, API, firmware, docs, tests, and venvLoad Templates: download a template from the default GitHub template repositoryEmpty Repository: create a minimal project folder with a starterREADME.md
Typical output looks like this:
01.my-project/
web/
api/
firmware/
docs/
tests/
venv/
.env.example
blueprint.json
.gitignore
Not every folder is created every time. The final layout depends on the mode and toggles you select.
- Python
gitpip- Internet access for cloud template downloads and remote Git pushes
- Project folders are numbered by scanning the current directory for existing folders that start with a number and a dot.
- Git push only works if the remote is reachable and your credentials are already configured.
- The tool is designed for local project scaffolding, not for managing production deployments.
The full software guide now lives on the documentation site:
If you are browsing the repo locally, the source markdown is still in docs/Documentation.md.
Template contribution guidance now lives on the contribution site:
If you are browsing the repo locally, the published markdown copy is in docs/contributing.md, and the root guide stays in CONTRIBUTING.md.