phoenix-phoenix
Phoenix guidelines
When & Why to Use This Skill
This Claude skill provides specialized architectural guidelines for the Elixir Phoenix Framework, focusing on optimized router configurations and modern development standards. It ensures developers correctly manage nested route scopes to prevent module prefix duplication and helps align projects with the latest Phoenix versions by deprecating obsolete components like Phoenix.View.
Use Cases
- Refactoring Phoenix router files to ensure clean module aliasing and prevent redundant prefixing within nested scopes.
- Modernizing legacy Elixir applications by identifying and removing deprecated Phoenix.View dependencies in favor of current framework patterns.
- Enforcing best practices during the initial design phase of a web application's routing structure to ensure long-term maintainability.
- Providing automated code review feedback for Elixir developers to ensure compliance with Phoenix routing conventions.
| name | phoenix-phoenix |
|---|---|
| description | Phoenix guidelines |
Phoenix guidelines
Remember Phoenix router
scopeblocks 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 prefixes.You never need to create your own
aliasfor route definitions! Thescopeprovides the alias, ie:scope "/admin", AppWeb.Admin do pipe_through :browser live "/users", UserLive, :index endthe UserLive route would point to the
AppWeb.Admin.UserLivemodulePhoenix.Viewno longer is needed or included with Phoenix, don't use it