skills.rest
hwatkins
hwatkinsCOMMUNITY
Explore all skills by this author →
GitHub

elixir-phoenix

Provide Elixir and Phoenix best-practice patterns for scalable RESTful APIs, LiveView features, and OTP systems.

Updated Feb 16, 2026
Search Tags:#testing#elixir#functional-programming#phoenix#otp#liveview#coding-conventions
One-click install
npx skills add https://github.com/hwatkins/my-skills --skill elixir-phoenix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elixir-phoenix
Source: https://github.com/hwatkins/my-skills/tree/main/skills/elixir-phoenix
Command: npx skills add https://github.com/hwatkins/my-skills --skill elixir-phoenix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elixir and Phoenix projects often struggle with maintaining clean architecture, clear boundaries, and consistent patterns across teams; this Skill provides structured guidance on functional core design, naming conventions, and robust context organization.

Core Features & Use Cases

  • Functional core design with pure computations and side effects isolated at boundaries.
  • Context-oriented organization: clear boundaries around business logic and APIs, with module naming conventions.
  • LiveView integration and OTP patterns: guidelines for concurrency, processes, and real-time interfaces.

Quick Start

Create a new Phoenix project and implement a simple module using the functional core pattern, then run the test suite.

Frequently Asked Questions about elixir-phoenix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure an Elixir and Phoenix project to maintain clean architecture and clear boundaries?▼

To maintain clean architecture in Elixir and Phoenix, apply functional core design with pure computations and isolate side effects at boundaries. This approach ensures clear module organization and consistent patterns across teams.

What is the best way to organize contexts in Phoenix for clear business logic boundaries?▼

The best way to organize contexts in Phoenix is by establishing clear boundaries around business logic and APIs using consistent module naming conventions. This structure isolates functional cores and simplifies complex domain interactions.

How do I integrate Phoenix LiveView with OTP patterns for robust real-time features?▼

To integrate Phoenix LiveView with OTP patterns, follow provided guidelines for concurrency and process management to build robust real-time interfaces. This combination handles state and real-time updates reliably.

Can I use static analysis and coding conventions to enforce Elixir OTP patterns across my codebase?▼

Yes, you can enforce Elixir OTP patterns across your codebase by applying structured coding conventions and static analysis requirements. This ensures consistent module organization and clean architecture throughout the application.

When should I isolate side effects at boundaries in functional Elixir programming?▼

You should isolate side effects at boundaries in functional Elixir programming when implementing functional core design. This pattern keeps pure computations separate, making your Phoenix application scalable and easier to test.

Related Skills

Explore More Software Engineering Skills→
CJ-1981CJ-1981

moai-lang-elixir

Provide Elixir 1.17+ and Phoenix 1.7 development guidance with code examples.

Community
Advanced
ArdurAIArdurAI
1

god-dev-codebase

Automate codebase review, security audits, and performance analysis.

Official
Advanced
thkim2015thkim2015

moai-lang-elixir

Assist Elixir 1.17+ development with Phoenix, LiveView, Ecto, and OTP patterns.

Community
Advanced
pbdeuchlerpbdeuchler
13

functional-core-imperative-shell

Enforce Functional Core and Imperative Shell boundaries with file classification comments.

Community
Intermediate