メニュー
Use when working in Wendy Labs repos, especially wendy-agent, WendyOS, samples, templates, or cloud docs, and the task needs orientation on Wendy CLI, agent, gRPC, runtime, or app deployment paths.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 creating a Wendy app from an existing Wendy template or sample, especially when the user names an app archetype such as realsense-camera, camera-feed, camera-feed-yolo, voice-assistant, audio, fullstack, simple-api, or asks to create a Wendy app in a new directory.
Use when a developer needs to install, verify, or repair the Wendy CLI before using `wendy run`, `wendy discover`, or device workflows.
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.
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.
| name | wendy-codebase |
| description | Use when working in Wendy Labs repos, especially wendy-agent, WendyOS, samples, templates, or cloud docs, and the task needs orientation on Wendy CLI, agent, gRPC, runtime, or app deployment paths. |
Use this workflow for Wendy CLI, wendy-agent, WendyOS, and sample app tasks.
pwd, git status --short --branch, and git remote -v.AGENTS.md and CLAUDE.md if present. Treat local instructions as authoritative for paths, device access, and publish preferences.rg/rg --files before broad directory walking. Avoid generated proto files unless the task is about generated surfaces.In wendy-agent:
go/cmd/wendy/main.go.go/internal/cli/commands/root.go.wendy run flow: go/internal/cli/commands/run.go.go/internal/cli/commands/helpers.go.go/internal/cli/grpcclient/client.go.go/internal/cli/providers/.wendy.json schema logic: go/internal/shared/appconfig/.go/internal/shared/discovery/.go/cmd/wendy-agent/main.go.go/internal/agent/services/.go/internal/agent/containerd/.go/internal/agent/oci/.Proto/; generated Go code: go/proto/gen/.The CLI is a Cobra application. Most device commands resolve a target, create a typed gRPC client, then call one of the agent services. The agent starts a plaintext gRPC server on port 50051, may start an mTLS server on 50052, registers agent/container/audio/video/provisioning/telemetry services, and uses containerd for app runtime work.
For app deployment, wendy run loads and validates wendy.json, resolves a target, builds with the appropriate provider, creates or updates a container on the agent through WendyContainerService, then starts the container and streams output back to the CLI.
wendy.json, trace from config parsing to the actual CLI or agent code path that consumes it.codes.Unimplemented as a normal compatibility path where possible.gofmt on touched files and targeted go test packages. Broaden tests when touching shared CLI, gRPC, or runtime behavior.cd /Users/maximilianalexander/wendylabsinc/wendy-agent/go
go test ./internal/cli/commands ./internal/agent/services
gofmt -w <changed-go-files>
wendy-dev --help
Use wendy-dev when testing the CLI from source if the user's local shell defines it.