菜单
Guidance for using PeiDocker built-in utility scripts. Use when Codex needs to choose installer or helper scripts, understand their parameters, place them in user_config.yml custom hooks, or reason about build-time versus runtime paths.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
New-user entrypoint and router for PeiDocker guidance. Use when Codex needs to orient a user who is new, unsure where to start, asking broad PeiDocker questions, or needing help choosing among project workflow, user_config.yml authoring, built-in utility scripts, and running configured projects.
Guidance for PeiDocker CLI project workflows. Use when Codex needs to install or verify pei-docker-cli, create projects, choose quick templates or build modes, run configure or remove, inspect generated project structure, or decide which generated project files are durable edit targets.
Guidance for operating a configured PeiDocker project. Use when Codex needs to build, run, stop, connect to, validate, troubleshoot, or clean up a PeiDocker project using Docker Compose, SSH, exec, GPU checks, or merged-build helper scripts.
Guidance for authoring PeiDocker user_config.yml files. Use when Codex needs to create or modify PeiDocker YAML for stages, images, SSH, ports, proxy, APT, environment variables, storage, mounts, devices, or lifecycle custom hooks.
| name | pei-docker-utility-scripts |
| description | Guidance for using PeiDocker built-in utility scripts. Use when Codex needs to choose installer or helper scripts, understand their parameters, place them in user_config.yml custom hooks, or reason about build-time versus runtime paths. |
Use this skill when the user wants to reuse PeiDocker's built-in scripts instead of writing custom shell from scratch.
Primary sources:
docs/manual/scripts/index.mddocs/manual/scripts/*.mddocs/manual/concepts/script-lifecycle.mddocs/manual/guides/custom-scripts.mdsrc/pei_docker/project_files/installation/stage-1/system/src/pei_docker/project_files/installation/stage-2/system/openspec/specs/install-script-parameter-interface/spec.mdopenspec/specs/installer-flag-conventions/spec.mdopenspec/specs/stage1-system-canonical-installers/spec.mdopenspec/specs/stage2-system-wrapper-policy/spec.mdPrefer canonical stage-1/system/* paths in config examples unless a source doc explicitly says otherwise. Most stage-2/system/* scripts are thin compatibility wrappers.
Read only the relevant reference file:
| Task | Reference |
|---|---|
| Pixi install, Pixi envs, package mirrors | references/pixi.md |
| Miniconda install, pip/conda mirrors, login activation | references/conda.md |
| ROS2 repository setup, ROS2 install, rosdep | references/ros2.md |
| OpenGL, OpenCV, vision tooling, GPU GUI workflows | references/opengl-opencv-vision.md |
| Node.js, UV, Bun, and other simple installers | references/node-uv-bun-simple-installers.md |
| Shell-level proxy helpers | references/proxy-helpers.md |
Use lifecycle timing before choosing a hook:
| Need | Hook |
|---|---|
| Install into image during build | custom.on_build |
| Initialize runtime storage once | custom.on_first_run |
| Reapply runtime setup every start | custom.on_every_run |
| Modify SSH login shell environment | custom.on_user_login |
| Replace default startup handoff | custom.on_entry |
Build-time script entries that need durable in-image paths should use /hard/image/.... Runtime hooks may use /soft/... after stage-2 storage links are prepared.
Add scripts under the relevant stage:
stage_2:
custom:
on_build:
- "stage-1/system/pixi/install-pixi.bash --user dev"
Script entries may include arguments. Preserve shell-like quoting when editing existing entries.
After adding or changing hook entries, run:
pei-docker-cli configure -p <project-dir>
If the user needs runtime verification, build and run using $pei-docker-run-project.