القائمة
Use when debugging WendyOS, Jetson, Raspberry Pi, USB-C host mode, containerd, GPU/audio/video entitlements, or a `wendy run` issue that only appears on a live device.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Expert guidance on building and deploying apps to WendyOS edge devices. Use when developers mention: (1) Wendy or WendyOS, (2) wendy CLI commands, (3) wendy.json or entitlements, (4) deploying apps to edge devices, (5) remote debugging Swift on ARM64, (6) NVIDIA Jetson or Raspberry Pi apps, (7) cross-compiling Swift for ARM64.
Use when creating, reviewing, or debugging `wendy.json` entitlements for Wendy apps, especially device access, networking, persistence, GPU, audio, camera, Bluetooth, USB, I2C, GPIO, SPI, serial, input, or MCP devices.
Use when creating, validating, or repairing a Wendy project scaffold, adapting Wendy templates, `wendy.json`, JSON schema setup, or project entitlements with `wendy init`, `wendy json`, or `wendy project entitlements`.
Use when a developer wants to build, deploy, run, detach, stream logs, start, stop, list, remove, or clean up Wendy apps with `wendy build`, `wendy run`, `wendy device apps list`, `wendy device logs`, telemetry streams, or volumes.
Use when a developer or coding agent needs Wendy CLI-native device operations: discover devices, set defaults, inspect device version/system/hardware/WiFi state, update the agent, or gather evidence before SSH/debugging.
Use when configuring, verifying, or explaining the Wendy CLI MCP server for AI assistants with `wendy mcp setup` or `wendy mcp serve`, especially Claude Code, Claude Desktop, Codex, or device-tool access.
| name | wendy-device-debug |
| description | Use when debugging WendyOS, Jetson, Raspberry Pi, USB-C host mode, containerd, GPU/audio/video entitlements, or a `wendy run` issue that only appears on a live device. |
Use this for live-device and cross-layer runtime bugs. Static code reading is not enough when the failure depends on device state.
wendy or source wendy-dev.wendy discover --json unless the user already supplied a hostname.wendy.json, entitlements, environment, startup logs.wendy-device-ops for CLI-native inspection before SSH when the agent and CLI can still answer the question.nerdctl, not Docker.For now, WendyOS devices may allow passwordless SSH as root@<hostname>. Treat this as break-glass diagnostic access for gathering evidence and filing issues in wendylabsinc/wendyos, not as the default way to mutate bare-metal settings.
Prefer fixes in the app container, wendy.json, CLI flow, agent service, or image repo. If you must change device state directly, keep the change minimal, explain why CLI/container paths were insufficient, and do not publish hostnames, credentials, tokens, or device-specific secrets in reusable output.
On the device, prefer read-only checks first:
hostname
cat /etc/wendyos/device-type 2>/dev/null || true
cat /etc/os-release 2>/dev/null || true
systemctl status wendy-agent --no-pager
journalctl -u wendy-agent -n 200 --no-pager
sudo nerdctl -n default ps -a
sudo nerdctl -n default logs <container>
test -f /etc/cdi/nvidia.yaml && sed -n '1,160p' /etc/cdi/nvidia.yaml
For Jetson GPU issues, verify all of:
/etc/wendyos/device-type exists and identifies a Jetson variant./etc/cdi/nvidia.yaml exists; on JetPack 5 (L4T r35, where nvidia-ctk predates CDI) the L4T CSV fallback (/etc/nvidia-container-runtime/host-files-for-container.d/*.csv) is used instead.wendy-agent/go/internal/cli/commands/helpers.go.wendy-agent/go/internal/cli/commands/run.go.wendy-agent/go/internal/shared/appconfig/.wendy-agent/go/cmd/wendy-agent/main.go.wendy-agent/go/internal/agent/services/container_service.go.wendy-agent/go/internal/agent/containerd/.wendy-agent/go/internal/agent/oci/entitlements.go.wendyos/.Give the root cause by layer. Distinguish what can be fixed in the repo now from what depends on device image state or host compatibility.