wao

Full build workflow — plan, build, test, validate. Manages tasks.json throughout every step. Use when user says 'build this', 'start building', 'implement this feature', or 'make this'. Not for single-file fixes — use /build-aos, /build-device, or /build-module directly.

Run in-memory AOS tests (legacynet units). Fast unit testing — no server needed. Use when testing AOS scripts or after code changes. Not for HyperBEAM integration tests — use /test-hb instead.

Write AOS scripts and comprehensive in-memory tests. Iterates until all tests pass 100%. Use when user says 'build the AOS script', 'write the Lua code', or 'implement the handler'. Not for scaffolding — use /create-aos.

Write HyperBEAM Erlang device with eunit tests. Iterates until compilation and tests pass 100%. Use when user says 'build the device', 'write the Erlang code', or 'implement the device'. Not for scaffolding — use /create-device.

Write Vite + React frontend components with comprehensive vitest tests. 100% pass required. Use when user says 'build the frontend', 'write the UI', or 'implement the components'. Not for dev server — use /dev.

Build custom WASM64 (Rust) or standalone Lua modules with HyperBEAM integration tests. Iterates until all tests pass 100%. Use when user says 'build the module', 'write the WASM', 'custom Lua module', or 'implement the module'. Not for AOS scripts — use /build-aos.

Scaffold a new AOS Lua script with its test file. Use when user says 'create a handler', 'new AOS script', 'scaffold a script', or 'add a handler'. Not for building full scripts with iteration — use /build-aos.

Scaffold a new HyperBEAM Erlang device with its test file. Use when user says 'create a device', 'new Erlang device', 'scaffold a device', or 'add a device'. Not for building full devices with iteration — use /build-device.

Scaffold a new custom module (WASM64 Rust or standalone Lua) with its test file. Use when user says 'create a module', 'new custom module', 'scaffold a WASM module', or 'scaffold a Lua module'. Not for AOS scripts — use /create-aos.

Troubleshoot WAO development issues. Diagnoses port conflicts, stale processes, missing dependencies, and common errors. Use when builds stall, tests hang, ports conflict, or user says 'something is broken', 'tests are stuck', or 'help debug'. Not for test failures — use /test or /test-hb to re-run tests.

Deploy AOS scripts to AO testnet, local HyperBEAM, or remote HyperBEAM. Use when user says 'deploy', 'ship it', 'push to mainnet', or 'go live'. Not for local testing — use /test-hb.

Start the Vite dev server for frontend development. Use when user says 'start the frontend', 'run dev server', or 'open the app'. Not for running tests — use /test-e2e for Playwright.

Plan a feature before building. Writes plan.md and tasks.json so any agent can pick up the work. Use when starting a new feature, user says 'plan this', 'design this', or 'what should we build'. Not for modifying existing plans — edit plan.md directly.

Generate a comprehensive README.md from the project's plan, code, and tests. Use when user says 'write the readme', 'document this', or 'generate docs'. Not for plan.md — use /plan.

Report progress on the current plan. Reads plan.md and tasks.json, shows status of each task and overall progress. Use when user says 'show progress', 'where are we', 'status', or 'what's done'. Not for running tests — use /validate.

Set up an agent team for parallel WAO development. Creates coordinated teammates for building features, researching patterns, debugging, or cross-layer work. Use when user says 'work in parallel', 'split the work', 'team up', or 'use multiple agents'.

Test HyperBEAM Erlang devices with WAO SDK integration tests. Launches real HyperBEAM and tests device via HTTP. Use when user says 'test the device', 'run device tests', or 'verify the Erlang module'. Not for eunit — use /build-device.

Playwright E2E tests with live HyperBEAM backend. Launches HB via WAO SDK, runs browser tests. Use when user says 'run E2E tests', 'test the frontend', or 'browser tests'. Not for vitest — use /build-frontend.

Run HyperBEAM integration tests. Starts a local Erlang HyperBEAM node and tests AOS processes on the full production stack. Use when user says 'test on HyperBEAM', 'run integration tests', or 'test the full stack'. Not for in-memory tests — use /test.

Post-build validation. Runs tests, checks Lua pitfalls, verifies AOS script coverage, and reports results. Use after building, before deploying, or when user says 'check everything', 'are tests passing', or 'validate'.