wordpress-php-guzzle-gutenberg-cursorrules-prompt- Cursor rule
Configures Cursor for WordPress plugins built with Guzzle, custom REST endpoints, and Gutenberg blocks. Enforces type hinting and WordPress standards.
.cursor/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdcWhat wordpress-php-guzzle-gutenberg-cursorrules-prompt- does
This rule instructs the AI to operate within a WordPress plugin architecture. It enforces WordPress coding standards across PHP, JavaScript, and TypeScript, requiring strict type hints on PHP code.
When writing scripts, the rule directs the agent to choose TypeScript over plain JavaScript. It favors functional paradigms and composition over inheritance, keeping solutions aligned with WordPress ecosystem conventions and prioritizing readability.
Because the configuration sets alwaysApply: false, Cursor will not attach these guidelines to every prompt automatically.
What it helps with
- create typed WP REST API endpoints
- make external HTTP requests using Guzzle
- build Gutenberg editor blocks with TypeScript
- format PHP and JavaScript to WordPress standards
Example prompts for the agent
- Add a new WP REST API endpoint with parameter validation
- Write a Guzzle HTTP client wrapper to query remote webhooks
- Create a custom Gutenberg block using TypeScript
How to install wordpress-php-guzzle-gutenberg-cursorrules-prompt-
Manually: put the files in place
.cursor/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdManually: put the files in place
.clinerules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about wordpress-php-guzzle-gutenberg-cursorrules-prompt-
How to install wordpress-php-guzzle-gutenberg-cursorrules-prompt- in Cursor?
Save the rule configuration into .cursor/rules/wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdc in your project root.
What does this rule do?
It guides the assistant to write WordPress plugin code following core standards, PHP type hinting, and TypeScript for Gutenberg blocks.
Does the rule apply to every prompt automatically?
No, the rule defines alwaysApply: false, so Cursor activates it based on matching context rather than every single request.
Source text
wordpress-php-guzzle-gutenberg-cursorrules-prompt-.mdc · CC0-1.0
--- 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.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules