use-pixi
Skill207 starsChanged 38 days agoApache-2.0View on GitHub
Use when explaining, creating, or changing a Pixi workspace, including manifests, dependencies, platforms, targets, features, environments, tasks, lockfiles, editable Python packages, CI commands, or IDE interpreter setup.
- Installs packages
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/unsafe-checker/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/rust-rustrover-cargo.mdcCursor rule
- ast-grepSkill
- auv-wayland-renderingSkill
- create-prSkill
- domain-cliSkill
- domain-cloud-nativeSkill
- domain-mlSkill
- domain-webSkill
- m01-ownershipSkill
- m02-resourceSkill
- m03-mutabilitySkill
- m04-zero-costSkill
- m05-type-drivenSkill
- m06-error-handlingSkill
- m07-concurrencySkill
- m09-domainSkill
- m10-performanceSkill
- m11-ecosystemSkill
- m12-lifecycleSkill
- m13-domain-errorSkill
- m14-mental-modelSkill
- m15-anti-patternSkill
- rust-call-graphSkill
- rust-code-navigatorSkill
- rust-deps-visualizerSkill
- rust-refactor-helperSkill
- rust-symbol-analyzerSkill
- rust-trait-explorerSkill
- simple-englishSkill
- unsafe-checkerSkill
- use-buf-pluginsSkill
- use-bufSkill
- use-protobufSkill
- auvSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 8 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use Pixi as the command and environment boundary for this repository.
- Very specific: line 12
Run pixi --version, pixi info, and pixi task list when available.
- Very specific: line 14
Read the selected manifest, its workspace.platforms, targets, features, environments, tasks, and editable path dependencies.
- Very specific: line 15
Read pixi.lock when reproducibility or CI behavior matters.
- Very specific: line 19
Put Python itself and command-line/system packages supplied by conda-forge under Pixi dependencies.
- Very specific: line 20
Put Python distributions resolved from PyPI under pypi-dependencies or [project.dependencies], according to the repository's existing …
- Very specific: line 22
Use target.<platform> for dependencies limited to one supported platform.
- Distinctive: line 23
Use a feature when a dependency set is optional and reusable.
- Very specific: line 24
Do not use bare pip install inside a Pixi-managed repository.
- Distinctive: line 37
Use the smallest applicable commands:
- Very specific: line 52
When adding or removing a dependency, use --feature FEATURE for a named feature and --platform PLATFORM for a platform-specific table.
- Distinctive: line 56
Keep the lockfile immutable in CI:
- Distinctive: line 73
Keep all declared platforms solvable.
- Distinctive: line 74
Do not add CUDA or another platform-only dependency to unconditional common dependencies.
- Distinctive: line 75
Do not remove or regenerate unrelated environments.
- Distinctive: line 76
Do not claim success until the lockfile is current and the requested task passes.
- Very specific: line 83
Keep the default environment to Ruff and ty with no python, solvable on linux-64, osx-arm64, and win-64.
- Very specific: line 86
Run pixi run --locked check before handoff when Python files or Pixi metadata change.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use Pixi
Use Pixi as the command and environment boundary for this repository.
Inspect before editing
- Run
pixi --version,pixi info, andpixi task listwhen available. - Locate both
pixi.tomlandpyproject.toml. Pixi discovers an explicit--manifest-pathfirst, then a localpixi.toml, then a localpyproject.toml, then parent manifests. A siblingpixi.tomltherefore wins overpyproject.toml. - Read the selected manifest, its
workspace.platforms, targets, features, environments, tasks, and editable path dependencies. - Read
pixi.lockwhen reproducibility or CI behavior matters. Do not hand-edit the lockfile.
Choose the dependency owner
- Put Python itself and command-line/system packages supplied by conda-forge under Pixi
dependencies. - Put Python distributions resolved from PyPI under
pypi-dependenciesor[project.dependencies], according to the repository's existing ownership boundary. - Represent a local Python project as
{ path = ".", editable = true }or another relative editable path in Pixi. - Use
target.<platform>for dependencies limited to one supported platform. - Use a feature when a dependency set is optional and reusable; compose features into named environments.
- Do not use bare
pip installinside a Pixi-managed repository. Usepixi add, a manifest edit, and a new lock instead.
Understand the model
- A workspace declares channels and every platform solved into
pixi.lock. - A target narrows configuration to a platform such as
linux-64,win-64, orosx-arm64. - A feature groups optional dependencies, tasks, activation, and targets.
- An environment selects features and produces an installable prefix under
.pixi/envs/by default; named or detached configuration may select another prefix. - A task is a reproducible command executed inside an environment.
- The lockfile records exact conda and PyPI resolutions for every declared platform.
Make and verify changes
Use the smallest applicable commands:
pixi add PACKAGE
pixi add --pypi PACKAGE
pixi remove PACKAGE
pixi remove --pypi PACKAGE
pixi update PACKAGE
pixi install
pixi run TASK
pixi shell # interactive use only
pixi task list
pixi lock --checkWhen adding or removing a dependency, use --feature FEATURE for a named feature and --platform PLATFORM for a platform-specific table. Combine the selectors only when both scopes apply.
For local, intentional manifest changes, run pixi lock, the relevant pixi run task, and pixi lock --check. Inspect the manifest diff and lockfile diff before reporting success.
Keep the lockfile immutable in CI:
pixi install --locked
pixi run --locked TASK--locked prevents lockfile updates; it does not make environment installation or task execution read-only. Inspect task definitions before running them in any no-write workflow.
CI must not run pixi lock, because that command mutates the lockfile.
IDE boundary
Run pixi install before selecting an interpreter. In AUV, .pixi/envs/default only carries Ruff and ty; select the named environment that owns a package (under .pixi/envs/) as the VS Code python.defaultInterpreterPath folder when analyzing or debugging it. Locate named or detached environments using the prefix reported by pixi info --json, but never commit the returned absolute machine path. Documentation, automation, and terminal commands should use pixi run; Windows and POSIX interpreter paths differ.
Safeguards
- Keep all declared platforms solvable; do not validate only the current host.
- Do not add CUDA or another platform-only dependency to unconditional common dependencies.
- Do not remove or regenerate unrelated environments.
- Do not claim success until the lockfile is current and the requested task passes.
AUV workspace
- Pixi is required only for Python or model work. Do not ask Rust, JavaScript, Protobuf, or documentation contributors to install it.
- The root
pixi.tomlowns Python tooling; Rust, pnpm, and Buf keep their own toolchains. Never add them topixi.toml. - Python package metadata owns runtime dependencies. Edit the package
pyproject.toml, then runpixi lock. - Keep the
defaultenvironment to Ruff and ty with nopython, solvable onlinux-64,osx-arm64, andwin-64. Do not add a workspace-wide Python pin. - Give each Python package its own feature that pins
pythonand its dependencies, and compose it into a named environment. Do not share asolve-groupbetween packages that need different Python versions. - For a package on another Python version, add a directory
ruff.tomlthat extends the root one with its owntarget-version, and run ty in that package's environment. - Run
pixi run --locked checkbefore handoff when Python files or Pixi metadata change.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

