القائمة
Debug Arizona stream operations. Use when investigating stream insert/delete/update/move/sort/reset behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | debug-stream |
| description | Debug Arizona stream operations. Use when investigating stream insert/delete/update/move/sort/reset behavior. |
| argument-hint | ["handler_module"] |
| allowed-tools | Read, Grep, Glob |
Debug stream operations in $ARGUMENTS.
Find how the stream is created in mount/1:
arizona_stream:new/1,2,3Find the ?each(Fun, Source) call in render/1:
Find handle_event/3 clauses that modify the stream:
arizona_stream functions are called (insert, delete, update, move, sort, reset)clear_stream_pending/2 is called after diffTrace how arizona_diff:diff_stream/4 processes pending ops:
OP_INSERT, OP_REMOVE, OP_ITEM_PATCH, OP_MOVEapply_limit/5compute_reorder_ops)Reference files:
src/arizona_stream.erlsrc/arizona_eval.erl (render_stream_item, eval_stream_items)src/arizona_diff.erl (diff_stream, diff_stream_pending, diff_stream_op)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.