菜单
This skill should be used when working with "Phoenix LiveView", "Plug pipelines", "controllers", "JSON APIs", "channels", "streams", "forms", "phx-hook", "authentication", or debugging "Phoenix/LiveView gotchas"
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeffweiss/elixir-production --skill phoenix-liveview命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
This skill should be used when choosing "data structures", "Map vs ETS vs gb_trees performance", evaluating "hash functions", needing "HyperLogLog or bloom/cuckoo filters", or comparing OTP built-ins against specialized alternatives for Elixir
This skill should be used when code is hard to understand, a module has "too many parameters or deep nesting", "functions exceed 40 lines", "abstractions feel leaky", or evaluating "deep-module vs shallow-module" design per Ousterhout principles
This skill should be used when building "multi-node Elixir systems", choosing between "Raft and CRDTs", configuring "libcluster or Partisan", debugging "split-brain or netsplit scenarios", evaluating "CP vs AP tradeoffs", investigating "data loss" in distributed pipelines, working with "Kafka", "RabbitMQ", "Broadway", or "PubSub" message delivery guarantees, or designing "event streaming" architectures
正在显示 SKILL.md
基于 SOC 职业分类
| name | phoenix-liveview |
| description | This skill should be used when working with "Phoenix LiveView", "Plug pipelines", "controllers", "JSON APIs", "channels", "streams", "forms", "phx-hook", "authentication", or debugging "Phoenix/LiveView gotchas" |
Start with server-rendered HTML. Escalate through streams, assign_async, PubSub, and hooks only when simpler patterns can't do the job. For non-LiveView needs (APIs, mobile clients), use Plug pipelines and Channels.
| Level | Need | Pattern |
|---|---|---|
| L0 | Display data | Assigns in mount/3 |
| L1 | User interaction | phx-click, push_navigate/2 |
| L2 | Forms | to_form/2 + changeset |
| L3 | Dynamic lists | Streams (stream/3, stream_insert/4) |
| L4 | Real-time updates | PubSub, assign_async/3 |
| L5 | Browser APIs | phx-hook |
else if in HEEx — use case/cond or :if attributesid MUST match stream nameconnected?(socket) for PubSub@form[:email] not @form.emailid — element MUST have unique idphx-feedback-for removed (LV 1.0) — use used_input?/1phx-page-loading removed (LV 1.0) — use page_loading: true in JS.push/2Read the file that matches your current problem:
escalation-ladder.md — When: Deciding which LiveView pattern level to use. Full L0-L5 with code examples, auth scopes, testingreferences/streams.md — When: Rendering dynamic lists or paginating data. Stream patterns and paginationreferences/forms.md — When: Building forms, uploads, or nested inputs. Form patterns including uploads and nested formsreferences/hooks.md — When: Integrating JavaScript libraries or browser APIs. JavaScript hooks with third-party library integrationreferences/authentication.md — When: Implementing auth, sessions, or authorization. Authorization, session management, magic link authreferences/advanced-patterns.md — When: Using assign_async, attach_hook, or managing reconnection. assign_async, attach_hook widgets, reconnect state managementreferences/plug-and-controllers.md — When: Building JSON APIs or Plug pipelines (non-LiveView). Plug pipelines, JSON APIs, fallback controllers, rate limitingreferences/channels.md — When: Need WebSockets, Presence, or real-time outside LiveView. Phoenix Channels, WebSockets, Presence, when Channels vs LiveView/feature <desc> — Guided feature implementation with TDD/review [file] — Review code against production standards