nonslop
AI-native project scaffolding.
The idea
The new way to bootstrap projects is skills. Instead of language-specific scaffolding tools, you start with a skills-ready project and compose what you need. Skills are universal -- they work across any project, any language, and any AI coding agent.
Quick start
uvx nonslop create-project my-project
Creates a new my-project/ directory in the current working directory, pre-wired with skill infrastructure. Two skills are preinstalled:
- ns-skill-management -- manage persistent skills with
npx skills - ns-skillx -- invoke any skill ephemerally from a GitHub repo, like
npxfor skills
Example: creating a Python project
From your new project, invoke skillx to scaffold a Python package:
In Claude Code:
/ns-skillx nseng-ai/nonslop --skill ns-create-pypackage-project
In Codex:
$ns-skillx nseng-ai/nonslop --skill ns-create-pypackage-project
The skill is fetched, executed, and discarded -- your project gets the Python scaffolding without permanently installing anything.
What you get
After create-project, your project has:
my-project/
├── .agents/skills/ # installed skills (universal agent directory)
├── .claude/ # Claude Code config + skill symlinks
├── AGENTS.md # project instructions for agents
├── CLAUDE.md # project instructions
├── nonslop.json # agents this project targets
├── skills-lock.json # installed skill metadata
└── .gitignore
Development
uv sync
just check
Metadata
Release files for nonslop 0.1.5
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 | Actions |
|---|---|---|---|---|
| nonslop-0.1.5.tar.gz | 17.4 kB | Without provenance | Details for nonslop-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nonslop-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for nonslop-0.1.5-py3-none-any.whl |
Total release size: 46.0 kB
Release files / nonslop-0.1.5.tar.gz
| Download URL | nonslop-0.1.5.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8175369a68f4264449b23bfa5c11a1c93c5b67b8552881d8d5a449c9cc213cd9
|
|
BLAKE2b-256 checksum How to use checksums |
83e684d0f7ddca7ee1a7c8fffd96d93446f72368377ca43778697b921ab29148
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / nonslop-0.1.5-py3-none-any.whl
| Download URL | nonslop-0.1.5-py3-none-any.whl |
|---|---|
| Size | 28.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ed73fdcee9fd6712007fc5719e39aaac6a8b4fb830c9a4aff94a395004de2f0
|
|
BLAKE2b-256 checksum How to use checksums |
25c47c77757791dbb404523bb01d9fd897b7a0b29ca54b289ee423d76e43f0b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for nonslop 0.1.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.