phoenix

Phoenix Elixir framework with LiveView for real-time. Use for Elixir apps.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

phoenix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Phoenix Elixir framework with LiveView for real-time. Use for Elixir apps.

Teams using phoenix should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/phoenix/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/frameworks/phoenix/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/phoenix/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How phoenix Compares

Feature / Agent	phoenix	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Phoenix Elixir framework with LiveView for real-time. Use for Elixir apps.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Phoenix

Phoenix (Elixir) provides real-time scalability (millions of connections). v1.7 + **LiveView** allows building rich SPAs without writing JavaScript.

## When to Use

- **Real-time**: Chat apps, live dashboards (Channels).
- **High Concurrency**: Leveraging the BEAM VM (Erlang).
- **Low JS**: LiveView handles the UI state on the server.

## Core Concepts

### LiveView

Server-rendered HTML that updates over WebSockets. "The server is the state source".

### Ecto

The database wrapper. Using `Changeset` for validation.

### PubSub

Built-in, distributed publish-subscribe system.

## Best Practices (2025)

**Do**:

- **Use Verified Routes**: `~p"/users/#{@user}"` ensures compile-time link safety.
- **Use Tailwind**: Default in 1.7.
- **Use Function Components**: HEEx templates with declarative assigns.

**Don't**:

- **Don't use SPA unless needed**: LiveView covers 95% of use cases.

## References

- [Phoenix Documentation](https://www.phoenixframework.org/)