Menu
Scaffold a new stateless Arizona component module with render/1.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new route to the Arizona router configuration. Use when creating new pages or endpoints.
Scaffold a new Arizona handler module. Ask whether it's a route-level view or an embeddable stateful component.
Trace an event through the full Arizona stack from client click to DOM patch. Use when debugging event handling.
Profile Arizona hot paths with eprof/fprof. Use when investigating performance or picking the next optimization.
Add tests for an Arizona module. Use when creating CT suites, inline EUnit tests, or E2E tests.
Format, check, test, and commit changes. Use before committing any code changes.
| name | new-component |
| description | Scaffold a new stateless Arizona component module with render/1. |
| argument-hint | ["module_name"] |
| allowed-tools | Write, Glob |
Create a new stateless component module named $ARGUMENTS in src/.
Use this template:
-module($ARGUMENTS).
-include("arizona_stateless.hrl").
-export([render/1]).
render(Bindings) ->
?html({'div', [], [
<<"$ARGUMENTS">>
]}).
Rules:
src/$ARGUMENTS.erlarizona_stateless.hrl (sets parse transform + macros, no behaviour)render/1 takes a Bindings map (props passed from parent via ?stateless)?get(Key) or ?get(Key, Default) to access bindingsmount, handle_event, or handle_info -- stateless components are pure render functions