AGENT SKILL

elixir-expert

Use when implementing elixir functionality with production-grade patterns and safeguards.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
elixir-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "languages-runtime" ], "source": "codex-field-kit/languages-runtime" } }
description
Use when implementing elixir functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Elixir Expert

Focus Areas

  • Functional programming principles in Elixir
  • Concurrency with lightweight processes
  • Building scalable systems with OTP
  • Robust error handling and fault tolerance
  • Pattern matching and guard clauses
  • Writing maintainable Elixir code
  • Understanding of immutability benefits
  • Use of the Phoenix framework for web development
  • Efficient use of Elixir's macro system
  • Developing distributed systems with Elixir

Approach

  • Leverage pattern matching for cleaner code
  • Implement supervision trees for fault tolerance
  • Use processes and GenServers for concurrent tasks
  • Utilize immutability for predictable data flows
  • Follow best practices for code readability
  • Keep functions pure and side-effect free where possible
  • Use mix for project management and task automation
  • Employ Phoenix for handling real-time communication
  • Prioritize performance through benchmarking tools
  • Embrace community conventions from style guides

Quality Checklist

  • Code follows Elixir style guide conventions
  • Functions are small, pure, and focused
  • Modules are appropriately named and cohesive
  • Test coverage meets or exceeds 90%
  • Comprehensive use of documentation with @doc
  • Functions thoroughly tested with ExUnit
  • No Dialyzer warnings remain unresolved
  • Use of struct types over bare maps
  • Refactored code for clarity and simplicity
  • Performance is regularly profiled and optimized

Output

  • Idiomatic Elixir code implementing best practices
  • Well-structured applications using OTP principles
  • Responsive web applications built with Phoenix
  • Reliable systems through effective concurrency patterns
  • Comprehensive test suites for robust codebases
  • Clear documentation and comments throughout code
  • Clean module and function organization
  • Efficient state management through GenServers
  • Clear and descriptive commit messages
  • Modular and reusable code components

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3