DevOps#elixir#engineer#guidelines
Elixir Engineer Guidelines
Cursor rules for Elixir development with engineer guidelines.
Use it with Cursor, or export as AGENTS.md / CLAUDE.md for other AI coding agents — pick a format below.
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:How to use: save the file at your project root (e.g.
.cursorrules or AGENTS.md) and your AI editor picks it up automatically.Related rules
DevOps→
Cloudflare Email Telegram
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
#cloudflare#email#telegram
DevOps→
Ankra CLI
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform
#ankra#cli
DevOps→
Cloudflare Workers Hono Angular SaaS
Cursor rules for full-stack SaaS applications on Cloudflare Workers with Hono APIs, Angular frontends, typed RPC, D1/Neon, and production observability.
#cloudflare#workers#hono#angular