Skip to main content
affpapa.org
RU EN
rule

elixir-engineer-guidelines — Cursor rule

A Cursor rule that frames work as senior Elixir engineering and sets a change-message format. Useful for Phoenix projects using the listed stack.

Install into Cursor · Manually: put the files in place All methods and platforms ↓ 
.cursor/rules/elixir-engineer-guidelines-cursorrules-prompt-file.mdc
Open on GitHub

What elixir-engineer-guidelines-cursorrules-prompt-file does

This rule tells Cursor to act as a senior Elixir engineer. It targets files matching **/* and provides context for Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, Ecto, ExUnit, Plug, and Phoenix LiveView.

The stack list also includes Credo, Sobelow, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, and ExCoveralls. Change messages follow a structure with a type, optional scope, description, body, and footer. The rule has alwaysApply: false, so it is not enabled automatically.

What it helps with

  • shape change messages consistently
  • keep Elixir and Phoenix context in coding tasks
  • define a change area with scope
  • format message details and footers

Example prompts for the agent

  • Write a change message for adding LiveView using this rule’s format.
  • Review this Phoenix task with the stack defined by the rule.
  • Format the change with type, scope, body, and footer.

How to install elixir-engineer-guidelines-cursorrules-prompt-file

Manually: put the files in place

.cursor/rules/elixir-engineer-guidelines-cursorrules-prompt-file.mdc

Frontmatter: description, globs, alwaysApply

Step by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules

Questions about elixir-engineer-guidelines-cursorrules-prompt-file

How do I install elixir-engineer-guidelines-cursorrules-prompt-file in Cursor?

Place the rule at .cursor/rules/elixir-engineer-guidelines-cursorrules-prompt-file.mdc in the project.

What does elixir-engineer-guidelines-cursorrules-prompt-file do?

It gives Cursor a senior Elixir engineering role, lists the project stack, and defines a format for change messages.

Does the rule apply automatically to every file?

It targets **/*, but alwaysApply: false means automatic application is disabled.

Source text

elixir-engineer-guidelines-cursorrules-prompt-file.mdc · CC0-1.0 
---
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:

© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules

Similar IDE rules

All IDE rules for Programming languages →
elixir-expert VoltAgent Community Reviews an Elixir project and helps implement changes using OTP, Phoenix, and Ecto. Use it when you need to reason about process architecture, fault handling, or tests. 167installs elixir Mindrally A skill that tells your coding agent how to write Elixir and Phoenix: functional patterns, Ecto, LiveView, OTP. Useful when the project actually runs on BEAM. CX Codex +1 836installs phoenix Mindrally Tells the agent how to write Elixir and Phoenix code: LiveView, Ecto, contexts, tests. Useful once the project is already on Phoenix. CX Codex +1 722installs ecto-patterns Claude MPM Team A skill that feeds your agent Ecto conventions for Phoenix apps: schemas, changesets, migrations, transactions and multi-tenancy. CX Codex +1 336installs phoenix-api-channels Claude MPM Team A Claude skill that walks the agent through Phoenix: JSON controllers, Ecto contexts, Channels and Presence on the BEAM. CX Codex +1 339installs sentry-elixir-sdk getsentry A skill that walks you through Sentry setup in an Elixir project: it scans mix.exs, proposes a feature set and hands you the configs. CX Codex +1 2,000installs

From the same set210

es-module-nodejs-guidelines-cursorrules-prompt-fil Cursor rule for Node.js development with ES module syntax. It enforces short responses, prioritizes task steps, and controls verbosity via Vx flags. ★ 41,024repo stars engineering-ticket-template-cursorrules-prompt-file This Cursor rule turns development requests into structured engineering tickets with implementation details, acceptance criteria, and testing notes. ★ 41,024repo stars embedded-stm32-hal A Cursor rule that keeps the agent inside embedded C/C++ conventions: STM32 HAL, interrupts, DMA and tight memory budgets. ★ 41,024repo stars elixir-phoenix-docker-setup-cursorrules-prompt-fil Configures Cursor for Elixir and Phoenix development inside Docker. Enforces senior engineering practices, Conventional Commits, and quick replies via the VV prefix. ★ 41,024repo stars dragonruby-best-practices-cursorrules-prompt-file A Cursor rule that sets Ruby coding style for DragonRuby Game Toolkit: naming, file structure, error handling. ★ 41,024repo stars docker Cursor rule enforcing production Docker practices. Generates minimal, hardened containers with non-root users, layer caching, and pinned base images. ★ 41,024repo stars deno-integration-techniques-cursorrules-prompt-fil This rule gives Cursor context for Deno automation scripts and workflows. It fits repositories built around the @findhow packages. ★ 41,024repo stars database A Cursor rule with database practices for Prisma and Supabase: schemas, migrations, queries, RLS policies. Scoped to database files by glob. ★ 41,024repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor