elixir engineer guidelines
Cursor rules for Elixir development with engineer guidelines.
La skill
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:
Cómo instalarla
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.
¿Te funcionó?
Inicia sesión para escribir aquí.De dónde viene
and Related Rights in the Work and the meaning and intended legal