Cursor Elixir 编码规范

Model: qwen-max | ¥0.15/call

AI工具GPT-4.1智能助手CursorElixir

Cursor Elixir 编码规范：来自 PatrickJS/awesome-cursorrules (40k stars) 的 eli，适用于各类文档与内容的智能化处理。

Calls: 1

Skill Documentation

Cursor Elixir 编码规范

摘要

Cursor Elixir 编码规范：来自 PatrickJS/awesome-cursorrules (40k stars) 的 eli，适用于各类文档与内容的智能化处理。

**文件来源:** PatrickJS/awesome-cursorrules → `rules/elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc`

**原仓库:** https://github.com/PatrickJS/awesome-cursorrules

**评分:** ⭐ 仓库 40k stars (社区最权威 Cursor rules 合集)

这个 skill 是干什么的?

把 `elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc` 这条 Cursor 编码规则打包成可调用的 AI skill,帮你把代码生成统一到一致的标准上。

> Cursor rules for Elixir development with Phoenix and Docker integration.

🤖 Agent 使用说明

**输入:** 一段要生成/重构的代码需求
**输出:** 严格遵守 `elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc` 规则的代码
**触发:** 用户说"用 X 规范写代码" / "按 elixir 风格生成" / "用 PatrickJS 的 X 规则"

👤 用户需要做什么?

[ ] 知道这条规则适合用在什么场景(参考下面"适用场景")
[ ] 把规则原文内容应用到 IDE 项目的 `.cursor/rules/` 目录(直接复制 .mdc 文件)
[ ] 调本 skill 时说清楚你的代码任务(语言/框架/目标)
[ ] 输出后人工 review 风格是否符合预期

适用场景

想用统一规范生成 `elixir` 项目代码
团队需要把 AI 代码生成收敛到固定风格
学习业界最佳实践的工程化模板

原始规则内容

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/awesome-cursorrules (40,581 stars, 257 个 .mdc 规则)
抓取时间: 2026-08-17
License: 跟随原仓库(MIT)

联系方式

有问题或建议,在本 skill 下留言。

FAQ

这个 skill 是干什么的?

把 `elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc` 这条 Cursor 编码规则打包成可调用的 AI skill,帮你把代码生成统一到一致的标准上。

> Cursor rules for Elixir development with Phoenix and Docker integration.

👤 用户需要做什么?

[ ] 知道这条规则适合用在什么场景(参考下面"适用场景")
[ ] 把规则原文内容应用到 IDE 项目的 `.cursor/rules/` 目录(直接复制 .mdc 文件)
[ ] 调本 skill 时说清楚你的代码任务(语言/框架/目标)
[ ] 输出后人工 review 风格是否符合预期

Open AIMS China Panel