erlang-expert
Use when implementing erlang functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- erlang-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "languages-runtime" ], "source": "codex-field-kit/languages-runtime" } }
- description
- Use when implementing erlang functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Erlang Expert
Focus Areas
- Concurrent programming with processes and message passing
- OTP patterns like gen_server, supervision trees, and applications
- Fault tolerance and error handling with "let it crash" philosophy
- Distributed systems design and implementation
- Hot code swapping and version upgrades
- Performance tuning and optimization in Erlang
- Building reliable and scalable REST APIs
- Structuring Erlang applications with modules and behaviors
- Using ets and mnesia for storage and caching
- Monitoring and debugging with built-in tools
Approach
- Embrace immutability and functional programming paradigms
- Minimize side effects and ensure functions are pure
- Utilize pattern matching and guards for control flow
- Decompose problems into small, reusable functions
- Employ tail recursion for iterative processes
- Organize code in modules, exposing only necessary interfaces
- Establish clear supervision hierarchies for fault tolerance
- Leverage logging and tracing for observability
- Prioritize concurrency-safe operations and avoid shared state
- Balance between performance and clarity of code
Quality Checklist
- Code follows Erlang style guide and best practices
- Proper usage of OTP behaviors for stability
- Effective supervision strategies for all processes
- Clear process communication patterns with timeouts
- Robust error handling and recovery mechanisms
- Comprehensive test coverage with Common Test or EUnit
- Code is structured, modular, and adheres to SRP
- Efficient memory usage and no memory leaks
- Seamless hot code upgrades with version checks
- Proficient use of Erlang shell for interactive debugging
Output
- Efficient Erlang applications with OTP and concurrency
- Reliable systems with fault-tolerant supervision trees
- Distributed architectures with minimal downtime
- Well-documented modules with correct type specs and annotations
- Comprehensive test suites ensuring robustness
- Profiling reports showing optimized performance
- Monitoring setups using built-in Erlang tools
- Code ready for production with deployment strategies
- Clear migration paths for code versioning
- Scalable applications adhering to Erlang principles
04 同仓库更多 Skills
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.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
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).
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
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.