php-drupal-development-standards

A set of coding standards for PHP projects that use Drupal, a content-management system for building websites. It encourages PHP 8.3 features and practices such as strict typing, typed properties, return types, immutable values, and explicit dependency handling.

In plain words
What is it for?
Use it when developing or reviewing Drupal modules, hooks, classes, and other PHP files that should follow consistent type-safety and maintainability rules.
Why use it?
It helps teams write PHP code that is easier to check, understand, maintain, and less likely to fail because of unexpected data types or unclear code structure.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/abderrahimghazali/cursor-rules/php-drupal-development-standards
Clone the repo
git clone --depth 1 https://github.com/abderrahimghazali/cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,070 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01070
Opus 5 $0.00000 $0.00535
Sonnet 5 $0.00000 $0.00214
Haiku 4.5 $0.00000 $0.00107

Measured yesterday against content hash c6fe46606e5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

php-drupal-development-standards scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/php-drupal-development-standards.mdc · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Enhanced PHP and Drupal Development Standards

Ensures adherence to PHP 8.3+ features and Drupal development best practices for improved code quality, security, and maintainability.

actions:

  • type: enforce conditions:

    • pattern: "^(?!declare\(strict_types=1\);)" message: "Add 'declare(strict_types=1);' at the beginning of PHP files for type safety."

    • pattern: "class\s+\w+\s*(?!\{[^}]*readonly\s+\$)" message: "Consider using readonly properties where immutability is required for better code safety."

    • pattern: "public\s+function\s+\w+\([^)]\)\s(?!:)" message: "Add return type declarations for all methods to enhance type safety."

    • pattern: "extends\s+\w+\s*\{[^}]public\s+function\s+\w+\([^)]\)\s*(?!#\[Override\])" message: "Add #[Override] attribute for overridden methods for clear intent."

    • pattern: "\$\w+\s*(?!:)" message: "Use typed properties with proper nullability to improve code readability and prevent errors."

    • pattern: "function\s+hook_\w+\([^)]\)\s(?!:)" message: "Add type hints and return types for all hooks to leverage PHP's type system."

    • pattern: "new\s+\w+\([^)]\)\s(?!;\s*//\s*@inject)" message: "Use proper dependency injection with services for better testability and modularity."

    • pattern: "extends\s+FormBase\s*\{[^}]*validate" message: "Implement proper form validation in FormBase classes for security."

    • pattern: "(?<!\bTRUE\b)\btrue\b|(?<!\bFALSE\b)\bfalse\b|(?<!\bNULL\b)\bnull\b" message: "Use uppercase for TRUE, FALSE, and NULL constants for consistency."

    • pattern: "(?i)\/\/\s[a-z]" message: "Ensure inline comments begin with a capital letter and end with a period for readability."

    • pattern: "\$this->config\('\w+'\)" message: "Use ConfigFactory for configuration management to ensure proper dependency injection."

  • type: suggest message: | PHP/Drupal Development Best Practices:

    • File Structure: Place module files in web/modules/custom/[module_name]/ for organization.
    • Module Files: Ensure modules include .info.yml, .module, .libraries.yml, .services.yml where applicable.
    • Dependencies: Use hook_requirements() to manage external dependencies.
    • Forms: Use FormBase or ConfigFormBase for creating forms, always include CSRF protection.
    • Caching: Apply proper cache tags and contexts for performance optimization.
    • Error Handling & Logging: Implement robust error handling and logging using Drupal's mechanisms.
    • Type Safety: Leverage type safety in form methods and throughout your code.
    • Dependency Injection: Follow Drupal's dependency injection patterns for better maintainability.
    • Service Container: Use Drupal's service container to manage dependencies.
    • Security: Validate all user inputs, use Drupal's security practices like sanitization and escaping.
    • Schema Updates: Implement hook_update_N() for database schema changes.
    • Translation: Use Drupal's t() function for all user-facing strings.
  • type: validate conditions:

    • pattern: "web/modules/custom/[^/]+/\.info\.yml$" message: "Ensure each custom module has a required .info.yml file."

    • pattern: "web/modules/custom/[^/]+/\.module$" message: "Ensure module has .module file if hooks are implemented."

    • pattern: "web/modules/custom/[^/]+/src/Form/\w+Form\.php$" message: "Place form classes in the Form directory for consistency."

    • pattern: "try\s*\{[^}]\}\scatch\s*\([^)]\)\s\{\s*\}" message: "Implement proper exception handling in catch blocks for robustness."

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 87 lines · 1,070 tokens per session scan A c6fe46606e5a

Subscribe to this mod's changes

php-drupal-development-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,070 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.