IDE Rule: Elixir Phoenix Docker Setupt Fil
IDE Rule: Elixir Phoenix Docker Setupt Fil is a verified IDE_RULE blueprint on Promptally in Framework IDE Rules optimized for leading AI models. Cursorrules_Mdc specification for IDE Rule: Elixir Phoenix Docker Setupt Fil. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Created by @promptallyTechnical Specifications
| Specification | Value |
|---|---|
| Artifact type | IDE RULE (Framework IDE Rules) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 544 |
| Source file | .cursorrules |
| Access tier | Free public (MIT) |
Pre-Filled Template
--- 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`)
How to use this ide rule
- Review the pre-filled example and source files above.
- Copy the template or download
.cursorrules, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use IDE Rule: Elixir Phoenix Docker Setupt Fil?
Open the ide rule on Promptally, review the pre-filled example, then copy the template or download .cursorrules and paste it into your model, IDE or workflow tool. IDE Rule: Elixir Phoenix Docker Setupt Fil is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is IDE Rule: Elixir Phoenix Docker Setupt Fil free?
Yes. IDE Rule: Elixir Phoenix Docker Setupt Fil is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does IDE Rule: Elixir Phoenix Docker Setupt Fil need?
IDE Rule: Elixir Phoenix Docker Setupt Fil is a static blueprint with no dynamic variables. Copy it and use it as-is.