diamond-setup
Universal Python project scaffold — generate professional, CI-ready skeletons in seconds.
No cookiecutter, no Jinja2, no magic. Just a clean CLI that produces a fully working project — uv sync, pytest, ruff, pre-commit and CI all wired up from second one.
Installation
pip install diamond-setup
# or
uv tool install diamond-setup
Usage
# New project with the minimal template (default)
diamond scaffold my-lib
# GenesisAeon preset (adds domains.yaml + entropy-table bridge)
diamond scaffold my-physics-tool --template genesis --author "Ada Lovelace"
# Preview what would be generated (no files written)
diamond scaffold my-lib --dry-run
# See all templates
diamond list-templates
# Validate any project directory
diamond validate path/to/my-project
diamond validate # validates the current directory
What you get
Running diamond scaffold my-lib produces:
my-lib/
├── src/
│ └── my_lib/
│ └── __init__.py # __version__ = "0.1.0"
├── tests/
│ ├── __init__.py
│ └── test_main.py
├── .github/
│ └── workflows/
│ └── ci.yml # matrix: 3.11 + 3.12
├── pyproject.toml # hatchling, ruff, pytest configured
├── README.md
├── AGENT.md # GenesisAeon release & metadata rules
├── .gitignore
└── .pre-commit-config.yaml # ruff + standard hooks
Then just:
cd my-lib
uv sync --dev
pre-commit install
uv run pytest
Templates
| Template | Description |
|---|---|
minimal |
Clean Python package for everyone |
genesis |
Adds domains.yaml + entropy-table bridge (GenesisAeon preset) |
Extending
Adding a new template is one Python file. See docs/templates.md.
Role in the GenesisAeon Ecosystem
diamond-setup is P-INFRA-1 in the GenesisAeon ecosystem registry —
the ecosystem infrastructure / template scaffold package. It generates the
standardized project skeletons (CI, packaging, pre-commit) used to bootstrap
new GenesisAeon packages, including the genesis preset that wires in the
entropy-table bridge.
Citation
Metadata
Release files for diamond-setup 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| diamond_setup-2.3.0.tar.gz | 97.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| diamond_setup-2.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 114.7 kB
Release files / diamond_setup-2.3.0.tar.gz
| Download URL | diamond_setup-2.3.0.tar.gz |
|---|---|
| Size | 97.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
599453e622a29db48d03158451d2666a53600432e81c834e84c78bda00e70c3f
|
|
BLAKE2b-256 checksum How to use checksums |
cfe7265966bf71567fc39df247c6e3b50e8e12c0ddc35fa983d114aad8528f64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / diamond_setup-2.3.0-py3-none-any.whl
| Download URL | diamond_setup-2.3.0-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c01e26e8f4cca0d00bb0c63ba2d0497de183158f7bf115101664e5a67f81af6b
|
|
BLAKE2b-256 checksum How to use checksums |
be7729a36254cc3d942642d73a5b91c8b1524a3b242ce6ad07cac11f30faf1fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logSecurity for diamond-setup 2.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for diamond_setup-2.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.