メニュー
Production deployment for Phoenix IDE. Use when running ./dev.py prod deploy, checking production status, diagnosing a failed deploy, or stopping the production service.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | phoenix-deployment |
| description | Production deployment for Phoenix IDE. Use when running ./dev.py prod deploy, checking production status, diagnosing a failed deploy, or stopping the production service. |
Run ./dev.py prod status to see which mode is active. Do NOT choose or configure the mode manually — ./dev.py prod deploy detects it automatically.
macOS
└── Native launchd mode (always)
Linux
└── systemd available? → YES → Native systemd mode
→ NO → Persistent bare-Linux supervisor
./dev.py prod deploy # Check, build, and deploy local HEAD
./dev.py prod deploy --release v1.2.3 # Deploy an exact checksummed release
./dev.py prod deploy --release latest # Deploy latest stable release
./dev.py prod status # Check runtime and durable transaction
./dev.py prod stop # Stop the backend-owned runtime
Local-HEAD deployment runs ./dev.py check first and aborts on failure. Published-release deployment verifies the selected target asset, checksum, tag commit, and embedded identity without compiling locally.
cargo run or start the binary directly — use ./dev.py prod deploysystemctl stop/start phoenix-ide or launchctl load/unload manually — ./dev.py prod deploy handles thisFor full details on each mode (ports, paths, log locations, LLM config), read the relevant file:
skills/phoenix-deployment/LAUNCHD.mdskills/phoenix-deployment/SYSTEMD.mdskills/phoenix-deployment/DAEMON.mdSee skills/phoenix-release/SKILL.md for the end-to-end flow (version bump, tag, CI build, sub-agent-drafted release notes).
Stable asset URLs use https://github.com/scottopell/phoenix-ide/releases/latest/download/phoenix_ide-<target> for supported macOS and Linux targets.
Implement, debug, test, and review changes in Phoenix IDE. Use for Phoenix coding tasks, repository workflow, validation, codegen, commits, or choosing the right specialized Phoenix skill. Start here for Work-mode tasks; use phoenix-explore first when the problem is still ambiguous.
Breadth-first, read-only investigation of ambiguous Phoenix IDE feedback and requests. Use in Explore mode to trace a raw symptom across easy-to-miss UI, runtime, wire, persistence, tool, worktree, and production boundaries before proposing an implementation task. Produces a bounded evidence-backed task, not code changes.
Cut a new phoenix-ide version by merging a version-bump PR, which triggers GitHub Actions to tag, build, and publish the binary, then replace the auto-generated release notes with a sub-agent-drafted, human-reviewable changelog. Use when the user says "cut a release", "publish a version", "ship vX.Y.Z", "tag a new release", or asks how to publish.
Finds one valid React performance target in the Phoenix UI. Profiles scenarios via the run-scenario harness (default transport: browser_profile), scans for known React anti-patterns, learns from db.yaml history, ranks, and returns a filled target.yaml. Use before /phoenix-perf-hunt.
Coordinates a Phoenix React performance attempt. Captures the scenario baseline (raw samples) BEFORE any change via the run-scenario harness (default transport: browser_profile), implements one focused fix, hands off to review, and records every outcome in db.yaml. Does not judge.
Add or update a Phoenix UI Ladle fixture end-to-end, including scenario data, stories, QA capture scripts, dev.py qa wiring, tests, and fixture best practices.