Home / Cursor rules / Elixir Engineer Guidelines

Elixir Engineer Guidelines

Cursor rules for Elixir development with engineer guidelines.

Cursor rules (.mdc)Public domain (CC0)

–unranked

Install

mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/elixir-engineer-guidelines-cursorrules-prompt-file.mdc -o .cursor/rules/elixir-engineer-guidelines.mdc

Downloads the file at commit b044f956f021 into .cursor/rules/.

To remove it later:

rm .cursor/rules/elixir-engineer-guidelines.mdc

Context cost: ≈198 tokens when used.

Rules file

---
description: "Cursor rules for Elixir development with engineer guidelines."
globs: **/*
alwaysApply: false
---
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:

Security

Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan