菜单
Use to push a Resident Lua app to a connected device. Accepts either a Lua file (push directly) or a natural-language description (chains through create-app + validate-app first, then pushes the result). Triggered by /resident:push-app or "push this app to my device".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | push-app |
| description | Use to push a Resident Lua app to a connected device. Accepts either a Lua file (push directly) or a natural-language description (chains through create-app + validate-app first, then pushes the result). Triggered by /resident:push-app or "push this app to my device". |
The user-facing entry point for getting Lua running on a Resident device. Accepts two shapes of input:
create-app to
generate the Lua, validate-app to check it, then push the result.This makes the common "I have an idea, run it on the device" path one
command. For tighter control, invoke create-app, validate-app, and
the push step independently.
You always need:
--device-id <id> — the deviceId your firmware reports (read it
off the device's screen, or check whatever your firmware persists).
Treat as an unguessable secret — anyone with the deviceId can push to
or read your device.--base-url <url> — defaults to https://resident.inanimate.tech
if not provided. Override for self-hosted relays
(e.g. http://localhost:8787 during wrangler dev).Both can be persisted across invocations:
RESIDENT_DEVICE_ID, RESIDENT_BASE_URL../.resident-device-id (deviceId only).Ask the user once per session if these aren't set; don't re-ask.
Device IDs that start with sim- target the in-browser simulator on
resident.inanimate.tech.
The simulator emulates an M5StickC Plus2 — a bundled DEVICE-SKILL.md
for that surface ships at
${CLAUDE_PLUGIN_ROOT}/skills/create-app/docs/m5stick/DEVICE-SKILL.md.
When the user-supplied device ID starts with sim- AND no
--device-skill was provided AND no ./DEVICE-SKILL.md exists in cwd,
forward the bundled path to create-app (and to validate-app
if you're calling it directly) as --device-skill ${CLAUDE_PLUGIN_ROOT}/skills/create-app/docs/m5stick/DEVICE-SKILL.md.
This lets a marketplace user with no local Resident checkout push apps
to the simulator with zero setup.
If the user has their own ./DEVICE-SKILL.md in cwd, that takes
precedence — they presumably know what they're doing. The sim-
auto-forward is a convenience for the bare quick-start path.
If the user gives a Lua file path, OR a Lua source via stdin, OR a specific path that already exists, just push it:
"${CLAUDE_PLUGIN_ROOT}/skills/push-app/tools/push.sh" \
--base-url https://resident.inanimate.tech \
--device-id abc12345 \
device-apps/foo.lua
cat device-apps/foo.lua | "${CLAUDE_PLUGIN_ROOT}/skills/push-app/tools/push.sh" \
--base-url http://localhost:8787 \
--device-id abc12345
${CLAUDE_PLUGIN_ROOT} is set by Claude Code to the absolute path of the
installed plugin — always use it to reference bundled tools; the CWD is
the user's project, not the skill directory.
If the user gives a description (no file, no Lua source on stdin — just a sentence like "make the screen flash red on shake"):
Generate. Invoke /resident:create-app (the sibling skill) with
the description and an --out path under device-apps/<slug>.lua.
If the user also passed --device-skill <path> and/or one or more
--ref <path> flags to push-app, forward them verbatim to
create-app. If neither was passed AND the device ID starts with
sim- AND there's no ./DEVICE-SKILL.md in cwd, forward
--device-skill ${CLAUDE_PLUGIN_ROOT}/skills/create-app/docs/m5stick/DEVICE-SKILL.md
(the bundled simulator surface). That skill embeds the sandbox
docs, resolves DEVICE-SKILL.md (caller path → cwd → prompt), reads
any --ref files, and produces tight Lua source. It also chains
through /resident:validate-app automatically; a returned source
is already compile- and lifecycle-checked.
Push. Run ${CLAUDE_PLUGIN_ROOT}/skills/push-app/tools/push.sh
against the file produced in step 1.
Show the user the Lua you generated. They want to see it. Print the file path and a preview.
If create-app stops asking for a DEVICE-SKILL.md path, surface its prompt to the user verbatim and stop — don't try to skip validation or guess a path.
0 — sent (HTTP 200)1 — device not connected (HTTP 503)2 — environment / argument error (missing flag, file not found, no jq)3 — other HTTP error (full body printed to stderr)https://resident.inanimate.tech/devices/<id>/send
(provided as a default for developers).POST /devices/<id>/send with Content-Type: application/json and
body { "type": "app", "code": "<lua source>" }.wrangler dev, base-url is http://localhost:8787.Use when authoring a DEVICE-SKILL.md for a new Resident-based firmware project. Walks the user through hardware, Lua module surface, examples, and constraints. Triggered when the user says "write a device skill", "set up DEVICE-SKILL.md", or invokes /resident:write-device-skill.
Use to generate a Resident Lua app from a natural-language description. Reads embedded sandbox docs and the firmware project's DEVICE-SKILL.md to know the runtime surface, generates Lua source, validates it, and writes the result via --out (or stdout). Triggered by /resident:create-app or "write a Lua app for this device".
Use to validate a Resident Lua app locally before pushing to a device. Runs the app through a local lua interpreter with auto-deduced stubs and checks for compile errors, missing lifecycle functions, and runtime errors during a few simulated ticks. Triggered by /resident:validate-app or when the user asks "validate this app".
Sanity check that the resident plugin loaded. Invoke when the user types "hello resident" or asks to verify the resident plugin is working.