php-expert
Use when implementing php functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- php-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "languages-runtime" ], "source": "codex-field-kit/languages-runtime" } }
- description
- Use when implementing php functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Php Expert
Focus Areas
- Leveraging PHP 8+ features like match expressions, attributes
- Mastering object-oriented programming principles
- Employing work with sessions and cookies securely
- Implementing PHP embedded templating effectively
- Utilizing error and exception handling paradigms
- Exploring advanced data structures within PHP
- Managing package dependencies with Composer
- Ensuring code quality with static analysis and linting
- Securing applications against common vulnerabilities
- Ensuring seamless integration with databases via PDO
Approach
- Start by prototyping with PHP's built-in development server
- Keep code DRY using reusable functions and classes
- Prioritize clear and self-documenting code practices
- Maintain separation of concerns using Design Patterns
- Regularly refactor code for readability and maintenance
- Optimize database queries for performance within PHP
- Use environment-specific configurations via
.envfiles - Execute thorough testing using PHPUnit for code reliability
- Integrate version control efficiently with Git
- Ensure output escaping to prevent XSS attacks
Quality Checklist
- Confirm code adheres to PSR standards for coding style
- Ensure PHPDoc comments for all methods and properties
- Validate input rigorously to prevent injection vulnerabilities
- Unit tests executed with >90% code coverage
- Validate session handling to prevent fixation attacks
- Confirm efficient memory usage through profiling
- Employ PHPCS and PHPMD for code quality assurance
- Verify responsiveness in error handling with consistent feedback
- Analytics tracked with minimal performance overhead
- Code auditing for security with automated tools
Output
- Robust and maintainable PHP codebase
- Comprehensive documentation with usage examples
- Detailed reports on test coverage and performance
- Error logs monitored and actionably managed
- Clearly structured file and directory organization
- Efficient data-access layers with adaptable connection options
- Localization and internationalization for diverse reach
- View templates processed with optimized rendering
- Logging access and error data for debugging and insights
- Configured CI pipeline for continual code integration and testing
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.