메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | create-device |
| description | 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. |
| argument-hint | <device-name> |
| disable-model-invocation | true |
Scaffold a new HyperBEAM Erlang device with its test file.
The argument $ARGUMENTS is the device name (required). It should be lowercase and will be used as the module name.
Read docs/hyperbeam-dev.md for the device template and protocol.
Create the Erlang device at HyperBEAM/src/dev_{name}.erl:
-module(dev_{name}).
-export([info/3, init/3, compute/3]).
-include("include/hb.hrl").
-define(STATE_KEY, <<"{name}-state">>).
info(_M1, _M2, _Opts) ->
{ok, #{
<<"name">> => <<"{name}">>,
<<"version">> => <<"1.0">>,
<<"endpoints">> => [<<"compute">>]
}}.
init(M1, _M2, Opts) ->
State = #{},
{ok, ID} = hb_cache:write(State, Opts),
M1Updated = hb_private:set(M1, #{?STATE_KEY => ID}, Opts),
{ok, M1Updated}.
compute(M1, M2, Opts) ->
Action = hb_maps:get(<<"action">>, M2, <<"default">>, Opts),
case Action of
<<"get">> -> handle_get(M1, M2, Opts);
_ -> {error, #{<<"status">> => 400, <<"error">> => <<"Unknown action">>}}
end.
handle_get(M1, _M2, _Opts) ->
{ok, maps:merge(M1, #{<<"result">> => <<"ok">>})}.
Where {name} is the argument (e.g., counter).
test/{name}.device.test.js:import assert from "assert"
import { describe, it, before, after } from "node:test"
import { HyperBEAM, HB, acc } from "wao/test"
describe("{Name} Device", function () {
let hbeam, hb
before(async () => {
hbeam = await new HyperBEAM({ reset: true }).ready()
hb = await new HB({ url: hbeam.url }).init(acc[0].jwk)
})
after(async () => hbeam.kill())
it("should respond to get", async () => {
const result = await hb.g("/~{name}@1.0/compute", { action: "get" })
assert.ok(result)
})
})
cd HyperBEAM && rebar3 compile
yarn test test/{name}.device.test.js