Elixir DX Development Rules

Code style and testing guidelines for Elixir development following DX library patterns for AST recompilation.

Code Style and Structure

General Principles

Pattern Matching

Example:

```elixir

def process({:ok, data}), do: transform(data)

def process({:error, reason}), do: handle_error(reason)

def process(nil), do: {:error, :invalid_input}

```

Code Organization

Function Definitions

```elixir

Preferred: one-line syntax when clauses are short

def status(:active), do: "User is active"

def status(:inactive), do: "User is inactive"

Use defd without parentheses

defd calculate_result data do

# function body

end

```

Testing Guidelines

Test Structure

File Organization

```

lib/

my_app/

users/

manager.ex

test/

my_app/

users/

manager_test.exs

```

Test Module Naming

```elixir

Ensure unique module names across all test files

defmodule MyApp.Users.ManagerTest do

use ExUnit.Case

# tests here

end

```

Implementation Notes

This skill focuses on AST recompilation patterns in Elixir. Follow these guidelines when working with:

The emphasis on functional patterns and immutability ensures code reliability when dealing with AST manipulation and recompilation workflows.