elixir-pro

18.0k

sickn33

Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems.

moai-lang-elixir

776

modu-ai

Elixir 1.17+ development specialist covering Phoenix 1.7, LiveView, Ecto, and OTP patterns. Use when developing real-time applications, distributed systems, or Phoenix projects.

elixir-antipatterns

214

Gentleman-Programming

Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing. Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code.

usage-rules

167

bradleygolden

Search for package-specific usage rules and best practices from Elixir packages. Use when you need coding conventions, patterns, common mistakes, or good/bad examples for packages like Ash, Phoenix, Ecto, etc.

hex-docs-search

167

bradleygolden

Research Hex packages (Sobelow, Phoenix, Ecto, Credo, Ash, etc). Use when investigating packages, understanding integration patterns, or finding module/function docs and usage examples. Automatically fetches missing documentation and source code locally.

elixir-architect

108

maxim-ist

Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration

phoenix-thinking

106

georgeguimaraes

This skill should be used when the user asks to "add a LiveView page", "create a form", "handle real-time updates", "broadcast changes to users", "add a new route", "create an API endpoint", "fix this LiveView bug", "why is mount called twice?", or mentions handle_event, handle_info, handle_params, mount, channels, controllers, components, assigns, sockets, or PubSub. Essential for avoiding duplicate queries in mount.

elixir-thinking

106

georgeguimaraes

This skill should be used when the user asks to "implement a feature in Elixir", "refactor this module", "should I use a GenServer here?", "how should I structure this?", "use the pipe operator", "add error handling", "make this concurrent", or mentions protocols, behaviours, pattern matching, with statements, comprehensions, structs, or coming from an OOP background. Contains paradigm-shifting insights.

ecto-thinking

106

georgeguimaraes

This skill should be used when the user asks to "add a database table", "create a new context", "query the database", "add a field to a schema", "validate form input", "fix N+1 queries", "preload this association", "separate these concerns", or mentions Repo, changesets, migrations, Ecto.Multi, has_many, belongs_to, transactions, query composition, or how contexts should talk to each other.

using-elixir-skills

106

georgeguimaraes

This skill should be used when the user works on any .ex or .exs file, mentions Elixir/Phoenix/Ecto/OTP, the project has a mix.exs, or asks "which skill should I use", "new to Elixir", "help with Elixir". Routes to the correct thinking skill BEFORE exploring code. Triggers on "implement", "add", "fix", "refactor" in Elixir projects.

oban-thinking

106

georgeguimaraes

This skill should be used when the user asks to "add a background job", "process async", "schedule a task", "retry failed jobs", "add email sending", "run this later", "add a cron job", "unique jobs", "batch process", or mentions Oban, Oban Pro, workflows, job queues, cascades, grafting, recorded values, job args, or troubleshooting job failures.

otp-thinking

106

georgeguimaraes

This skill should be used when the user asks to "add background processing", "cache this data", "run this async", "handle concurrent requests", "manage state across requests", "process jobs from a queue", "this GenServer is slow", or mentions GenServer, Supervisor, Agent, Task, Registry, DynamicSupervisor, handle_call, handle_cast, supervision trees, fault tolerance, "let it crash", or choosing between Broadway and Oban.

elixir-ecto-patterns

98

TheBushidoCollective

Use when Elixir Ecto patterns including schemas, changesets, queries, and transactions. Use when building database-driven Elixir applications.

dialyzer-analysis

98

TheBushidoCollective

Use when analyzing and fixing Dialyzer warnings and type discrepancies in Erlang/Elixir code.

ecto-query-patterns

98

TheBushidoCollective

Use when querying data with Ecto.Query DSL including where clauses, joins, aggregates, preloading, and query composition. Use for building flexible database queries in Elixir applications.

credo-custom-checks

98

TheBushidoCollective

Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.

credo-configuration

98

TheBushidoCollective

Use when configuring Credo static analysis for Elixir projects requiring customized code quality rules and settings.

ecto-schemas

98

TheBushidoCollective

Use when defining and working with Ecto schemas including field types, associations, and embedded schemas. Use when modeling database entities in Elixir.

elixir-otp-patterns

98

TheBushidoCollective

Use when Elixir OTP patterns including GenServer, Supervisor, Agent, and Task. Use when building concurrent, fault-tolerant Elixir applications.

ecto-schema-patterns

98

TheBushidoCollective

Use when defining data structures using Ecto schemas including fields, associations, embedded schemas, and schema metadata. Use for modeling domain data in Elixir applications.

credo-checks

98

TheBushidoCollective

Use when understanding and fixing common Credo check issues for Elixir code quality and consistency.

dialyzer-configuration

98

TheBushidoCollective

Use when configuring Dialyzer for Erlang/Elixir type checking and static analysis.

elixir-pattern-matching

98

TheBushidoCollective

Use when Elixir pattern matching including function clauses, case statements, with statements, and destructuring. Use for elegant control flow.

dialyzer-integration

98

TheBushidoCollective

Use when integrating Dialyzer into development workflows and CI/CD pipelines for Erlang/Elixir projects.

debug-to-fix

49

ElliotJLT

When debugging frustration appears ("why isn't this working?", "it should work", "I don't understand"), orchestrate the full debug cycle: clarify → investigate → fix → verify. Prevents the common failure of jumping to fixes before understanding the problem. An elixir that chains rubber-duck and prove-it with investigation.

elixir-expert

39

404kidwiz

Expert in Elixir, Phoenix Framework, and OTP. Specializes in building concurrent, fault-tolerant, and real-time applications using the BEAM. Use when building Elixir applications, working with Phoenix, implementing GenServers, or designing distributed systems on the BEAM.

elixir

23

Mindrally

Expert in Elixir and Phoenix development with functional programming patterns

phoenix

23

Mindrally

Phoenix framework development guidelines covering LiveView, Ecto, real-time features, and best practices for building scalable web applications with Elixir.

backend-development

23

Mindrally

Guidelines for backend development in C++ and Elixir/Phoenix, covering modern language features, best practices, and production-ready patterns.

elixir-ash-phoenix

20

benswift

Develops, debugs, and refactors Elixir web applications using Ash framework for resource management and Phoenix LiveView for the frontend. Uses tidewave MCP tools for debugging running applications. Use when working with Elixir, Ash, or Phoenix code.

ecto-patterns

15

bobmatnyc

Ecto patterns for Phoenix/Elixir apps. Covers schemas, changesets, migrations, queries, Ecto.Multi, transactions, constraints, associations, pagination, tenant partitioning, performance, and testing.

elixir-expert

15

oimiragieo

Elixir and Phoenix expert including OTP, Ecto, and functional programming

Supertester OTP Testing

13

nshkrdotcom

This skill should be used when teams need to adopt Supertester to build deterministic Elixir OTP tests with isolation, synchronization, and supervision coverage.

ExUnit Test Framework

10

FortiumPartners

Execute and generate ExUnit tests for Elixir projects with setup callbacks, describe blocks, and async testing support

Elixir Genius

9

agoodway

Use when designing or architecting Elixir/Phoenix/LiveView applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration

phoenix

9

TerminalSkills

Phoenix is an Elixir web framework built on the BEAM VM for fault-tolerant, real-time applications. It features LiveView for interactive UIs without JavaScript, channels for WebSockets, and Ecto for database access with compile-time query validation.

elixir-no-shortcuts

8

mkreyman

BLOCKS shortcuts like modifying dialyzer.ignore or .credo.exs excludes. Enforces fixing actual problems. Use when encountering ANY error, warning, or quality tool complaint.

elixir-discipline

8

mkreyman

MANDATORY pre-check before ANY response - ensures you use applicable skills and follow best practices. Use this skill FIRST before responding to any Elixir/Phoenix request.

elixir-quality-gate

8

mkreyman

Run comprehensive Elixir quality checks (format, credo, dialyzer, tests) with proper error handling and reporting. Use when validating code quality, before commits, or preparing for deployment.

elixir-root-cause-only

8

mkreyman

MANDATORY systematic debugging - trace to root cause before proposing fixes. NO random changes, NO symptom fixes, NO "try this". Use when debugging ANY error or issue.

elixir-verification-gate

8

mkreyman

MANDATORY verification before claiming anything works. Run actual commands, read actual output, provide evidence. Use when claiming tests pass, build succeeds, or code works.

phoenix-context-creator

8

mkreyman

Create complete Phoenix contexts following best practices including bounded contexts, proper API design, and comprehensive testing. Use when designing new features or refactoring code into contexts.

elixir-test-runner

8

mkreyman

Run ExUnit tests with smart filtering, debugging options, and proper error reporting. Use when running tests, debugging failures, or validating specific test cases.

phoenix-generator

8

mkreyman

Generate Phoenix resources (contexts, schemas, LiveViews, controllers) using mix phx.gen.* commands with best practices. Use when creating new Phoenix resources, contexts, or LiveView components.

elixir-no-placeholders

8

mkreyman

PROHIBITS placeholder code, default values that mask missing data, and silent failures. Enforces fail-fast with loud errors. Use when implementing ANY function or data structure.

elixir-tdd-enforcement

8

mkreyman

MANDATORY for ANY feature or bugfix - write ExUnit test FIRST, watch it FAIL, then implement. NO exceptions. Use before writing any Elixir production code.

ecto-migration-helper

8

mkreyman

Create, manage, and safely run Ecto database migrations with proper rollback handling and best practices. Use when working with database schema changes, adding columns, or modifying constraints.

swe-programming-elixir

7

wahidyankf

Elixir coding standards from authoritative docs/explanation/software-engineering/programming-languages/elixir/ documentation