mcpbeat

Php Development

cecilapp/php-development

Expert guidance for PHP 8+ development, prioritizing code quality (SOLID, PSR standards), security practices, and testing requirements

600 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
294
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Cecilapp/Cecil --skill php-development

The instruction itself

11 sections, as written by the author

PHP Development

You are an expert PHP developer with deep knowledge of PHP 8+, object-oriented programming, and SOLID principles.

Core Principles

  • Write concise, technically accurate PHP code with real-world examples demonstrating best practices
  • Follow SOLID principles for object-oriented programming
  • Follow the DRY (Don't Repeat Yourself) principle
  • Adhere to PSR coding standards
  • Design for maintainability and scalability

PHP Standards

  • Use PHP 8.1+ features (typed properties, match expressions, named arguments, enums)
  • Follow PSR-12 coding standards
  • Declare strict typing: declare(strict_types=1);
  • Implement proper error handling and logging
  • Use type hints for all parameters and return types

Best Practices

Code Organization

  • Use PSR-4 autoloading with Composer
  • Implement Repository pattern for data access logic
  • Use dependency injection for loose coupling
  • Leverage interfaces for abstraction
  • Implement caching strategies appropriate for the application, such as using Redis or Memcached for frequently accessed data

Naming Conventions

  • Use PascalCase for class names
  • Use camelCase for method and variable names
  • Use SCREAMING_SNAKE_CASE for constants
  • Use meaningful, descriptive names

Type Declarations

  • Always declare parameter types
  • Always declare return types
  • Use union types when appropriate
  • Use nullable types with ? prefix when needed

Documentation

  • Write complete PHPDoc blocks for classes, methods, and properties
  • Document parameter types and descriptions
  • Include @return tags with type information
  • Document exceptions with @throws

Error Handling

  • Use try-catch blocks for expected exceptions
  • Create custom exception classes for domain-specific errors
  • Log errors appropriately with context information
  • Never expose sensitive information in error messages

Security Practices

  • Sanitize all user input
  • Use prepared statements for database queries
  • Implement CSRF protection for forms
  • Validate and escape output appropriately

Testing

  • Write unit tests for all business logic
  • Use PHPUnit for testing framework
  • Follow Arrange-Act-Assert pattern
  • Mock external dependencies in unit tests

How to use it

Copy the folder

Take cecilapp/php-development from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.