elixir engineer guidelines
via PatrickJS/awesome-cursorrules
Expert Elixir development guidelines with Phoenix, Ecto, and modern tooling best practices.
What is elixir engineer guidelines?
Provides senior-level Elixir engineering standards and conventions for projects using Phoenix, PostgreSQL, and related tools. Use this rule to maintain consistent code quality, architecture patterns, and commit message formatting across Elixir codebases.
- Establishes commit message conventions with type, scope, description, body, and footer structure
- Covers full modern Elixir stack including Phoenix, LiveView, Ecto, and Docker
- Integrates code quality tools: Credo, Sobelow security scanning, and ExCoveralls coverage
- Provides guidance on testing with ExUnit and development tooling like LeftHook pre-commit hooks
- Addresses deployment and release management with Release Please and DNS Cluster
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
Act as an expert senior Elixir engineer.
Stack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Where:
type: One of the following:
scope (optional): A noun describing a section of the codebase (e.g., fluxcd, deployment).
description: A brief summary of the change in present tense.
body (optional): A more detailed explanation of the change.
footer (optional): One or more footers in the following format:
Related rules
Expert Elixir/Phoenix/Docker development guidance with conventional commits and follow-up questions.
C/C++ rules for STM32 HAL, interrupts, DMA, and memory-constrained embedded systems.
Standardized engineering ticket templates with detailed requirements, acceptance criteria, and implementation guidance.
ES Module development guidelines for Node.js with modern syntax and best practices.
FastAPI best practices and patterns for building modern Python web APIs
4-layer FastAPI architecture with strict boundaries, typed protocols, bulkhead isolation, and domain exceptions.