elixir-phoenix-docker-setup-cursorrules-prompt-fil

A set of coding guidelines for Elixir applications built with Phoenix, Docker, PostgreSQL, and related tools.

In plain words
What is it for?
Use it when building or changing Phoenix applications, database code, Docker setups, tests, security checks, and deployment-related files.
Why use it?
It gives the coding agent a defined technology stack and response style, reducing inconsistent implementation choices and missed project conventions.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/elixir-phoenix-docker-setup-cursorrules-prompt-fil
Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules
Per session 517 This file is loaded in full into every session.
When invoked 517 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00517 $0.00517
Opus 5 $0.00259 $0.00259
Sonnet 5 $0.00103 $0.00103
Haiku 4.5 $0.00052 $0.00052

Measured 3d ago against content hash 91edf273f4a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

elixir-phoenix-docker-setup-cursorrules-prompt-fil scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc · 44 lines

What it actually says

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

  • When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.

  • After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be thought-provoking and dig further into the original topic.

  • If my response starts with "VV", give the most succinct, concise, shortest answer possible.

Commit Message Guidelines:

  • Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure: [optional scope]: [optional body][optional footer(s)]

Where:

  • type: One of the following:

    • build: Changes that affect the build system or external dependencies (e.g., Maven, npm)
    • chore: Other changes that don't modify src or test files
    • ci: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)
    • docs: Documentation only changes
    • feat: A new feature
    • fix: A bug fix
    • perf: A code change that improves performance
    • refactor: A code change that neither fixes a bug nor adds a feature
    • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
    • test: Adding missing tests or correcting existing tests
  • 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:

    • BREAKING CHANGE: (for breaking changes)
    • <issue_tracker_id>: (e.g., Jira-123: Fixed bug in authentication)
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 44 lines · 0 tokens per session scan A 91edf273f4a2

Subscribe to this mod's changes

elixir-phoenix-docker-setup-cursorrules-prompt-fil is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 517 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.