wendy-lite

Overview of wendy-lite skill

What wendy-lite is for

wendy-lite is a skill for building WebAssembly apps that run on Wendy Lite firmware for ESP32-C6. It is most useful when you want to move from a rough embedded idea to a working WASM module that can talk to hardware through Wendy Lite’s host imports.

Who should use it

Use the wendy-lite skill if you are developing firmware-adjacent apps in C, Rust, Swift, Zig, TypeScript, or WAT and need device access, boot-time loading, or callback-driven behavior. It is especially relevant for wendy-lite for Backend Development only when “backend” means device-side logic, runtime integration, or app orchestration on the MCU.

What makes it different

Unlike a generic WASM prompt, wendy-lite is shaped around the actual runtime model: WAMR on ESP32-C6, wendy module imports, flash-stored binaries, and async callbacks such as GPIO interrupts, timers, and BLE events. That makes the skill more useful when the blocker is not “how do I write WASM?” but “how do I make this app fit the firmware contract?”

How to Use wendy-lite skill

Install and inspect the right files

Run the wendy-lite install flow for your directory, then read SKILL.md first. If you are extending the repo, also inspect any linked reference files named in the frontmatter, especially wasm-api.md, firmware-config.md, and swift-sdk.md. Those files are where the practical interface details usually live.

Give the skill a device-shaped brief

The best input is not “build me a WASM app,” but a device task with constraints: target language, hardware inputs and outputs, boot behavior, and whether the app must handle callbacks. For example: “Create a Rust WASM module for ESP32-C6 that reads a button on GPIO, toggles a NeoPixel, and survives reconnects.” That is much better than a vague wendy-lite usage prompt because it gives the skill the runtime shape it needs.

Start from the runtime contract

When using wendy-lite usage, think in this order: what the module exports, what it imports from wendy, how callbacks are handled, and how the binary is packaged for flash. If you are unsure, ask for a minimal skeleton first, then layer in hardware access and error handling after the runtime path is clear.

Practical workflow that reduces rework

1. State the language and target board.
2. Specify the hardware features you need: GPIO, I2C, SPI, UART, BLE, networking, or LED control.
3. Say whether you want a minimal starter, a full app, or a port from existing code.
4. Ask for any needed build notes, especially if you are using Swift or a nondefault toolchain.
   This is the fastest way to get a useful wendy-lite guide result instead of a generic WASM example.

wendy-lite skill FAQ

Is wendy-lite beginner-friendly?

Yes, if your goal is a constrained device app and you are willing to follow a runtime-specific workflow. It is less beginner-friendly if you need a broad WASM tutorial first, because wendy-lite assumes you care about firmware integration, not just language syntax.

When is wendy-lite a bad fit?

Skip the wendy-lite skill if you are not targeting ESP32-C6, do not need hardware access, or only want a normal web WASM app. It is also a weak fit if your project cannot store a WASM binary in flash or cannot use the WAMR-based execution model.

How is it different from a plain prompt?

A plain prompt often misses the contract between your code and the firmware. wendy-lite is better when you need correct import/export shapes, callback handling, or device lifecycle guidance that ordinary prompting tends to gloss over.

What should I verify before trusting the output?

Check whether the proposed code matches the actual host API, callback entry points, and build target in the repository. If the answer does not mention those pieces, it may be technically plausible but still wrong for Wendy Lite.

How to Improve wendy-lite skill

Provide the missing hardware details

The biggest quality jump comes from telling the skill exactly what hardware path you need. Mention the sensor or actuator, pin numbers if known, whether the event is interrupt-driven, and whether the app must persist state across reboots. That helps wendy-lite avoid producing a broad demo that does not match your board.

Ask for the right output shape

If you want to ship faster, ask for one of three output types: a minimal working module, a buildable example with notes, or a migration plan from an existing C/Rust/Swift/Zig project. Clear output shape matters more than a long prompt, especially when you need wendy-lite install results that are immediately testable.

Watch for common failure modes

The most common mistakes are assuming standard WASM browser APIs, skipping the wendy host import layer, or overlooking callback wiring for async events. If the first answer feels too abstract, ask the skill to rewrite it against the actual firmware lifecycle and to call out any unsupported assumptions.

Iterate with compile-first feedback

After the first pass, feed back the exact failure: missing import, wrong target triple, incorrect callback name, or build step mismatch. A strong wendy-lite guide iteration usually comes from one concrete error report plus a narrowed goal, not from asking for “more detail.”