agentleFS
niloykumarbarmanniloykumarbarman/EVERYTHING-CLAUDE-CODE/.cursor/rules/php-coding-style.md

EVERYTHING-CLAUDE-CODE / rules

Cursor rule1 starsChanged 7 months agoMITView on GitHub

PHP coding style extending common rules

We split this php-coding-style.md into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow PSR-12 formatting and naming conventions.

    line 12
  2. Very specific:

    Prefer declare(strict_types=1).

    line 13
  3. Distinctive:

    Use scalar type hints, return types, and typed properties everywhere new code permits.

    line 14
  4. Distinctive:

    Prefer immutable DTOs and value objects for data crossing service boundaries.

    line 18
  5. Very specific:

    Use readonly properties or immutable constructors for request/response payloads where possible.

    line 19
  6. Distinctive:

    Keep arrays for simple maps.

    line 20
  7. Distinctive:

    Use PHP-CS-Fixer or Laravel Pint for formatting.

    line 24
  8. Distinctive:

    Use PHPStan or Psalm for static analysis.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
php-coding-style.md

PHP Coding Style

This file extends the common coding style rule 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.