菜单
Phoenix 1.8 framework conventions covering layouts, routing, components, icons, forms, HTTP clients, and design file handling. Use when building or reviewing Phoenix web applications.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | phoenix-guidelines |
| description | Phoenix 1.8 framework conventions covering layouts, routing, components, icons, forms, HTTP clients, and design file handling. Use when building or reviewing Phoenix web applications. |
mix precommit alias when you are done with all changes and fix any pending issues:req (Req) library for HTTP requests. Avoid :httpoison, :tesla, and :httpc. Req is included by default and is the preferred HTTP client for Phoenix apps<Layouts.app flash={@flash} ...> which wraps all inner contentAppWeb.Layouts module is aliased in the app_web.ex file, so you can use it without needing to alias it againcurrent_scope assign:
current_scope to <Layouts.app>current_scope error by moving your routes to the proper live_session and ensure you pass current_scope as needed<.flash_group> component to the Layouts module. You are forbidden from calling <.flash_group> outside of the layouts.ex modulecore_components.ex imports an <.icon name="hero-x-mark" class="w-5 h-5"/> component for hero icons. Always use the <.icon> component for icons, never use Heroicons modules or similar<.input> component for form inputs from core_components.ex when available. Using it will save steps and prevent errors<.input class="myclass px-2 py-1 rounded-lg">) with your own values, no default classes are inherited, so your custom classes must fully style the inputscope blocks include an optional alias which is prefixed for all routes within the scope. Always be mindful of this when creating routes within a scope to avoid duplicate module prefixesalias for route definitions! The scope provides the alias:scope "/admin", AppWeb.Admin do
pipe_through :browser
live "/users", UserLive, :index
end
The UserLive route would point to the AppWeb.Admin.UserLive module.
Phoenix.View no longer is needed or included with Phoenix, don't use it.pen files directly as JSON blobs. These are design files that must only be modified through the Pencil MCP server toolsCore Elixir language guidelines covering common pitfalls like list access, immutability, module organization, struct access, date/time handling, and OTP patterns. Use when writing or reviewing Elixir code.
Ecto best practices covering preloading, schema types, changeset validation, field access, security, and migration conventions. Use when working with Ecto schemas, changesets, queries, or migrations.
Best practices for testing Elixir applications with Ecto.SQL.Sandbox, including background process handling, Oban testing, and test output quality. Use when writing or reviewing Elixir tests.
Phoenix HEEx template rules covering interpolation syntax, form building, class lists, conditional rendering, comments, and common anti-patterns. Use when writing or reviewing HEEx templates.
Phoenix LiveView patterns covering streams, JavaScript interop (hooks, colocated scripts, push events), testing, and form handling. Use when building or reviewing LiveView features.
Tailwind CSS v4 configuration and usage guidelines for Phoenix projects, plus UI/UX design principles. Use when styling Phoenix applications or building user interfaces.