Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Cursor rules for Elixir development with engineer guidelines.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✓→✗ | ▼ Worse | -35% | 0% |
| case-22 | ✓→✓ | ＝ Same ✓ | 10% | 0% |
| case-23 | ✓→✓ | ＝ Same ✓ | 10% | 0% |
| case-24 | ✓→✓ | ＝ Same ✓ | 27% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | -37% | 0% |
Cursor rules for Elixir development with engineer guidelines.
Synced from https://github.com/PatrickJS/awesome-cursorrules/tree/main/rules/elixir-engineer-guidelines-cursorrules-prompt-file.mdc.
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:
Other measured skills in the registry, with their headline benchmark lift.