What problem does it solve? Turning a Jac project into a distributable package is error-prone: the default scaffold layout produces empty wheels, jac.toml fields have hyphen-vs-underscore traps, and there is no built-in publish command. This Skill guides packaging a Jac project as a PEP 427 wheel for PyPI or an npm tarball, with correct metadata, entry points, and extras. ## Core Features & Use Cases - Wheel and sdist builds: Configure jac.toml ([project], [dependencies], [entrypoints.scripts], [optional-dependencies]) and run jac build --as wheel, then upload with twine to TestPyPI or PyPI. - npm publishing: Run jac build --as npm to compile client modules to ES modules with package.json and .d.ts files, respecting the sv server-boundary rejection rule. - Package layout guidance: Create the required package directory matching project.name, avoid listing jaclang as a dependency, and ship precompiled .jir bytecode. - Use Case: You finished a Jac CLI tool and want teammates to run jac install greet and get a greet command on PATH. This Skill walks you through the package directory, jac.toml metadata, the build, and the twine upload. ## Quick Start Package my Jac project as a wheel and show me the exact jac.toml and build commands to publish it to PyPI.
