Files
everything-claude-code/rules/php/coding-style.md
Sam Rook 113119dc6f feat: add laravel skills (#420)
* feat: add laravel skills

* docs: fix laravel patterns example

* docs: add laravel api example

* docs: update readme and configure-ecc for laravel skills

* docs: reference laravel skills in php rules

* docs: add php import guidance

* docs: expand laravel skills with more pattern, security, testing, and verification examples

* docs: add laravel routing, security, testing, and sail guidance

* docs: fix laravel example issues from code review

* docs: fix laravel examples and skills per review findings

* docs: resolve remaining laravel review fixes

* docs: refine laravel patterns and tdd guidance

* docs: clarify laravel queue healthcheck guidance

* docs: fix laravel examples and test guidance

* docs: correct laravel tdd and api example details

* docs: align laravel form request auth semantics

* docs: fix laravel coverage, imports, and scope guidance

* docs: align laravel tdd and security examples with guidance

* docs: tighten laravel form request authorization examples

* docs: fix laravel tdd and queue job examples

* docs: harden laravel rate limiting and policy examples

* docs: fix laravel pagination, validation, and verification examples

* docs: align laravel controller response with envelope

* docs: strengthen laravel password validation example

* docs: address feedback regarding examples

* docs: improve guidance and examples for pest usage

* docs: clarify laravel upload storage and authorization notes

* docs: tighten up examples
2026-03-16 13:35:23 -07:00

1.4 KiB

paths
paths
**/*.php
**/composer.json

PHP Coding Style

This file extends common/coding-style.md with PHP specific content.

Standards

  • Follow PSR-12 formatting and naming conventions.
  • Prefer declare(strict_types=1); in application code.
  • Use scalar type hints, return types, and typed properties everywhere new code permits.

Immutability

  • Prefer immutable DTOs and value objects for data crossing service boundaries.
  • Use readonly properties or immutable constructors for request/response payloads where possible.
  • Keep arrays for simple maps; promote business-critical structures into explicit classes.

Formatting

  • Use PHP-CS-Fixer or Laravel Pint for formatting.
  • Use PHPStan or Psalm for static analysis.
  • Keep Composer scripts checked in so the same commands run locally and in CI.

Imports

  • Add use statements for all referenced classes, interfaces, and traits.
  • Avoid relying on the global namespace unless the project explicitly prefers fully qualified names.

Error Handling

  • Throw exceptions for exceptional states; avoid returning false/null as hidden error channels in new code.
  • Convert framework/request input into validated DTOs before it reaches domain logic.

Reference

See skill: backend-patterns for broader service/repository layering guidance.