メニュー
Quick-start guide for new Capsem developers. Use when someone asks "how do I get started", "how to set up", "first time setup", or "bootstrap". Points to the bootstrap script and full docs. For detailed environment troubleshooting, use /dev-setup instead.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Capsem benchmarking with capsem-bench and capsem-bench-rs. Use when running benchmarks, adding new benchmark categories, interpreting results, or investigating performance regressions. Covers benchmark categories (disk, rootfs, storage, startup, protocol/http, snapshot, all), the JSON output format, and how to add new benchmarks.
Capsem development toolchain -- all just recipes, what they do, when to use which, and dependency chains. Use when you need to know how to build, run, test, or ship Capsem, or when deciding which just command to run for a given change. This is the toolchain reference.
Asset building, manifest format, hash verification, and boot-time resolution for Capsem VM images. Use when debugging boot failures, manifest issues, hash mismatches, or understanding how assets flow from build to boot.
Capsem native package installer -- package install, service registration, self-update, manifest-driven asset download, corp config provisioning, and the install test harness. Use when working on package install/update/uninstall commands, service install/uninstall, asset management, corp config, install test infrastructure, or the installed layout (~/.capsem/).
Capsem release process, CI pipeline, Apple code signing, notarization, documentation site, and post-release verification. Use when preparing a release, debugging CI failures, working with Apple certificates, updating the documentation site, or cutting a new version. Covers the full release lifecycle from pre-release checklist through post-release verification.
Capsem system architecture -- service daemon, per-VM processes, CLI, MCP server, guest agent, vsock, network proxy. Use when you need to understand the system design to write code, review changes, write documentation, or debug cross-component issues. Covers the service architecture, IPC protocols, vsock ports, storage modes, network policy, MITM proxy, and key source files.
| name | dev-start |
| description | Quick-start guide for new Capsem developers. Use when someone asks "how do I get started", "how to set up", "first time setup", or "bootstrap". Points to the bootstrap script and full docs. For detailed environment troubleshooting, use /dev-setup instead. |
git clone <repo> && cd capsem
./bootstrap.sh # interactive, prompts [Y/n] before each install
./bootstrap.sh --yes # non-interactive (CI / unattended setup)
just exec "echo hello" # verify VM boots (build-assets runs as part of bootstrap)
bootstrap.sh lives at the repo root, not under scripts/.
Three phases. Default answer at every prompt is Yes — press Enter to install, type n to skip.
bash, git, curl. Auto-installed: rustup (sh.rustup.rs), just (just.systems → ~/.local/bin).uv (astral.sh), uv sync, flock (brew on macOS), container runtime on macOS (colima + docker + docker-buildx via brew, then colima start --vm-type vz --vz-rosetta --memory 16 --cpu 8), pnpm install for the frontend.--fix (scripts/doctor-common.sh --fix): installs Rust targets, cargo-llvm-cov, cargo-audit, b3sum, cargo-tauri (= tauri-cli crate), cargo-sbom; builds VM assets and packs the initrd.Release-only local preflight also needs cdxgen. Install it with
npm install -g @cyclonedx/cdxgen before running
bash scripts/check-release-workflow.sh or local VM asset release dry runs.
--yes flag and non-tty input both auto-accept every prompt.
All just recipes (run, test, dev, etc.) check for .dev-setup and auto-run doctor if missing. You can't accidentally skip setup.
/dev-setup skill/dev-just/dev-testingDocker (via Colima on macOS) with 12GB+ RAM (16GB recommended -- the Tauri install-test build OOMs below 12GB). On Linux, Docker runs natively. See /dev-setup for configuration.