lua-expert
Use when implementing lua functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- lua-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "languages-runtime" ], "source": "codex-field-kit/languages-runtime" } }
- description
- Use when implementing lua functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Lua Expert
Focus Areas
- Understanding of Lua's metatables and metamethods
- Mastery of Lua table manipulation techniques
- Proficient in using coroutines for concurrency
- Knowledgeable in Lua's string manipulation facilities
- Handling errors using Lua's pcall and xpcall
- Familiarity with best practices for Lua module creation
- Memory management with Lua's garbage collector
- Writing efficient algorithms in Lua
- Debugging and profiling Lua code effectively
- Adopting Lua's functional programming paradigms
Approach
- Embrace Lua’s simplicity and avoid unnecessary complexity
- Leverage tables extensively as arrays, dictionaries, and structures
- Utilize coroutines for non-preemptive multitasking
- Employ string patterns for text processing tasks
- Encapsulate code in modules for reusability and organization
- Use metatables to extend and modify table behavior
- Optimize Lua scripts through profiling and targeted improvements
- Adopt a clear and consistent coding style
- Write scripts that are platform-independent
- Prioritize readability and maintainability of code
Quality Checklist
- Verify that all Lua scripts run without runtime errors
- Ensure proper use of local variables to prevent polluting global scope
- Maintain consistent indentation and style across codebase
- Test Lua code thoroughly with a variety of input scenarios
- Document code with comments explaining the logic and flow
- Profile Lua scripts to identify and address performance bottlenecks
- Validate Lua table data structures for expected schemas
- Confirm that modules correctly encapsulate functionality
- Analyze stack traces for error diagnosis and resolution
- Assess code for any unused or redundant code paths
Output
- Lua scripts that are efficient and adhere to best practices
- Modules that encapsulate Lua functionality for reuse
- Error-free execution with robust error handling mechanisms
- Clean and readable code with appropriate commenting
- Profiling reports highlighting performance optimizations
- Modular scripts with clear separation of concerns
- Code adhering to Lua community standards
- Scripts verified for memory and execution efficiency
- Comprehensive tests covering edge cases
- Consistent documentation for all functions and modules
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.