Skip to main content
affpapa.org
RU EN
rule

elixir-phoenix-docker-setup-cursorrules-prompt-fil: Cursor rule

Configures Cursor for Elixir and Phoenix development inside Docker. Enforces senior engineering practices, Conventional Commits, and quick replies via the VV prefix.

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

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

This rule primes Cursor to act as a senior Elixir engineer. It embeds a tech stack covering Phoenix LiveView, PostgreSQL, Ecto, Docker, Credo, and Sobelow. Before generating code, the assistant must analyze edge cases and system requirements.

Every full response ends with three bold follow-up questions labeled **Q1**, **Q2**, and **Q3**. When you need a quick answer without explanations, prefix your prompt with VV. The model will return only the bare minimum.

Commit suggestions adhere strictly to Conventional Commits with scopes and types like feat or fix. Because alwaysApply is set to false, Cursor does not inject these instructions into every single prompt automatically.

What it helps with

  • Draft Phoenix contexts and Ecto schemas with security checks
  • Generate structured Conventional Commit messages
  • Get instant single-line Elixir answers using the VV prefix
  • Explore architecture trade-offs using generated follow-up prompts

Example prompts for the agent

  • VV How do I run Ecto migrations inside the Docker container?
  • Create a Phoenix LiveView dashboard component with ExUnit tests.
  • Suggest a commit message for adding Credo and Sobelow CI checks.

How to install elixir-phoenix-docker-setup-cursorrules-prompt-fil

Manually: put the files in place

.cursor/rules/elixir-phoenix-docker-setup-cursorrules-prompt-fil.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-phoenix-docker-setup-cursorrules-prompt-fil

How to install elixir-phoenix-docker-setup-cursorrules-prompt-fil in Cursor?

Save the rule content into .cursor/rules/elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc in your project root.

What does this rule do?

It configures Cursor as a senior Elixir engineer across Phoenix, Ecto, and Docker. It mandates planning before coding and standardizes git commit formats.

How does the VV shortcut work?

Starting any prompt with VV instructs Cursor to skip background reasoning and provide the shortest possible reply.

Source text

elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc · CC0-1.0 
---
description: "Cursor rules for Elixir development with Phoenix and Docker integration."
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

- 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`)

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

Similar IDE rules

All IDE rules for Backend and APIs →
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 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 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 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 phoenix-ops Claude MPM Team A skill for getting a Phoenix app ready for production: releases, runtime config, clustering, telemetry and endpoint hardening. CX Codex +1 331installs

From the same set210

fastapi A Cursor rule for FastAPI work in Python. It guides project structure, API design, models, security, database code, testing, and deployment. ★ 41,024repo stars 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-engineer-guidelines-cursorrules-prompt-file A Cursor rule that frames work as senior Elixir engineering and sets a change-message format. Useful for Phoenix projects using the listed stack. ★ 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

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