Menu
A brief summary of the change in present tense.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/tomevault-io/skills-registry --skill cursor-rules-for-elixir-development-with-engineer-guidelinesThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
Based on SOC occupation classification
Showing SKILL.md
| name | Cursor rules for Elixir development with engineer guidelines |
| version | 1.0.0 |
| author | community |
| tags | ["cursorrules","community"] |
| compatibleModes | ["Build","Review","Ask"] |
| atlarixMinVersion | 7.0.0 |
Cursor rules for Elixir development with engineer guidelines.
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
[optional scope]:
[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:
Source: AmariahAK/atlarix-skills — distributed by TomeVault.
