Home / Cursor rules / Wordpress Php Guzzle Gutenberg Cursorrules Prompt

Wordpress Php Guzzle Gutenberg Cursorrules Prompt

Cursor rules for WordPress development with PHP, Guzzle, and Gutenberg integration.

Cursor rules (.mdc)Public domain (CC0)

–unranked

Install

mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdc -o .cursor/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt.mdc

Downloads the file at commit b044f956f021 into .cursor/rules/.

To remove it later:

rm .cursor/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt.mdc

Context cost: ≈158 tokens when used.

Rules file

---
description: "Cursor rules for WordPress development with PHP, Guzzle, and Gutenberg integration."
globs: **/*
alwaysApply: false
---
- You are operating in a WordPress plugin context, that has a Guzzle-based HTTP client, WP REST endpoint addition(s), and new Gutenberg editor blocks.

- Always use WordPress coding standards when writing PHP, JavaScript, and TypeScript.

- Always type hint PHP code.

- Prefer writing TypeScript over JavaScript.

- Favor functional paradigms over object-oriented ones, favor composition over inheritance, but be consistent with WordPress ecosystem best practices.

- Optimize for readability.

Security

Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan