adversarial-phoenix-liveview

• SKILL.mdcore · 9,828 bytes
• SKILL.mdcore · 9,828 bytes
• assets/templates/verdict.mddoc · 1,584 bytes
• gotchas.mddoc · 5,850 bytes
• metadata.jsonasset · 2,061 bytes
• references/_sections.mddoc · 7,147 bytes
• references/async-lifecycle-owned-tasks.mddoc · 2,502 bytes
• references/async-no-blocking-external-calls.mddoc · 2,295 bytes
• references/async-no-socket-in-closure.mddoc · 1,743 bytes
• references/async-render-failure-states.mddoc · 2,043 bytes
• references/bound-component-messaging.mddoc · 2,323 bytes
• references/bound-context-owns-data-access.mddoc · 2,012 bytes
• references/bound-function-component-first.mddoc · 2,212 bytes
• references/bound-myself-target.mddoc · 2,309 bytes
• references/flow-broadcast-from-context.mddoc · 2,623 bytes
• references/flow-presence-not-hand-rolled.mddoc · 2,970 bytes
• references/flow-scoped-topics.mddoc · 2,774 bytes
• references/render-assign-functions-only.mddoc · 1,644 bytes
• references/render-explicit-assign-passing.mddoc · 1,787 bytes
• references/render-keyed-comprehensions.mddoc · 2,111 bytes
• references/render-no-data-loading-in-template.mddoc · 2,110 bytes
• references/render-no-template-variables.mddoc · 1,657 bytes
• references/reviewer-prompt.mddoc · 9,791 bytes
• references/state-connected-guard.mddoc · 1,978 bytes
• references/state-form-recovery.mddoc · 2,099 bytes
• references/state-load-in-the-right-callback.mddoc · 2,180 bytes
• references/state-patch-over-remount.mddoc · 2,027 bytes
• references/stream-bounded-infinite-scroll.mddoc · 2,715 bytes
• references/stream-collections-not-assigns.mddoc · 2,371 bytes
• references/stream-dom-contract.mddoc · 2,000 bytes
• references/trust-authorize-every-event.mddoc · 2,595 bytes
• references/trust-disconnect-on-revocation.mddoc · 2,366 bytes
• references/trust-live-session-boundaries.mddoc · 2,340 bytes
• references/trust-scoped-lookups.mddoc · 2,230 bytes
• references/ui-focus-managed-overlays.mddoc · 2,260 bytes
• references/ui-hook-ignore-contract.mddoc · 2,142 bytes
• references/ui-inflight-feedback.mddoc · 2,092 bytes
• references/ui-js-commands-for-presentation.mddoc · 1,967 bytes
• references/ui-rate-bound-inputs.mddoc · 2,146 bytes

# Adversarial Phoenix LiveView Gate

A realtime-UI architecture review gate for Phoenix LiveView — pass/fail: a single blind reviewer subagent judges the work against this gate's rules with an adversarial mandate, and the work passes only when every rule is PASS or N/A. This skill renders verdicts; it never fixes the work.

The rules target one failure mode: **LiveView written as a page-controller bolted to a JS framework, instead of what it is — a stateful process rendering change-tracked diffs over a lossy socket**. Remounts that destroy state a patch would keep, broadcasts emitted where only one writer fires them, external calls that freeze the whole view, template constructs that silently disable change tracking, collections that grow per-socket memory without bound, events trusted because the button was hidden, and interactions designed against localhost latency. These all compile cleanly and demo perfectly; they surface as memory bloat, stale UIs, frozen views, and IDOR reports in production. Each rule carries an **Evidence of violation** paragraph so a reviewer can decide PASS/FAIL/N/A from artifact evidence alone. Sibling gates: `adversarial-beam` judges message-delivery semantics, `adversarial-elixir` judges paradigm fit — run all three for full coverage of substantial Phoenix work.

## When to Apply

- A Phoenix LiveView feature — live views, live components, HEEx templates, PubSub-driven UI updates, presence, infinite scroll — is about to merge and needs an objective PASS/FAIL on its realtime-UI architecture.
- An agent (Claude, Codex) authored LiveView code and you want an independent check that it did not fake realtime correctness — controller habits, unscoped topics, unbounded assigns, unauthorized event handlers, zero-latency assumptions.
- A LiveView app is being prepared for real traffic and the localhost-era assumptions (no latency, one node, small data, trusted clients) need to be surfaced as verdicts.
- A production incident (memory bloat, frozen view, IDOR, stale UI) was fixed at one site and you want the same class hunted across the affected area.

Do not apply to non-Phoenix codebases (the reviewer prompt's precondition aborts with "GATE NOT APPLICABLE"), or when the user wants explanations and refactors rather than a verdict. Version note: every FAIL trigger rests on LiveView 1.0+ APIs (streams, async, JS commands); the missing-`:key` leg is version-gated to LiveView 1.1+ (colocated hooks never trigger a FAIL), and `current_scope` spellings are Phoenix 1.8 scaffolding — pre-1.8 targets are judged on the underlying shape (actor-filtered access). The reviewer prompt carries the applicability axes.