wendy-agentic-coding

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.

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`, `wendy device logs`, telemetry streams, or volumes.

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, or input devices.

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 when preparing Wendy repo commits, GitHub PRs, review-thread cleanup, or CI fixes, especially for wendy-agent Go changes.