A comprehensive collection of WordPress development guidelines, coding standards, and best practices designed specifically for Large Language Models (LLMs) and AI-powered development tools.
This repository contains structured rules and patterns that help LLMs generate better WordPress code by following established conventions, security practices, and performance optimizations. The rules are organized into focused modules covering different aspects of WordPress development.
My plugin boilerplate uses this command to instruct AI to clone and add the rules: https://raw.githubusercontent.com/JUVOJustin/wordpress-plugin-boilerplate/refs/heads/main/.opencode/command/rules-upsert.md
This command is setup for github copilot and opencode integration. You can adjust the folders to your setup
- Copying Rules: You can copy rules from this repository to your LLM integration tool. Full control over the rules you want to use!
- MCP Server: Use the WordPress Dev Community MCP Server for seamless integration
My agency Citation Media does offer a free MCP Server. It serves the rules of this repo as well as other nice to have functionality. For Claude Desktop, Windsurf or Cursor add this to your MCP configuration:
{
"mcpServers": {
"wordpress-dev-docs": {
"command": "npx",
"args": [
"mcp-remote",
"https://wordpress-dev-mcp.citation.media/mcp"
]
}
}
}For Claude code use:
claude mcp add wordpress-dev-docs --transport http https://wordpress-dev-mcp.citation.media/mcp -s projectFor Github Copilot use:
{
"mcpServers": {
"wordpress-dev-docs": {
"type": "http",
"url": "https://wordpress-dev-mcp.citation.media/mcp",
"tools": [ "*" ]
}
}
}We encourage contributions from the WordPress development community! If you have rules, patterns, or best practices that would benefit other developers, please consider opening a Pull Request.
- Fork this repository
- Create a new branch for your changes
- Add your rules following the existing format and structure
- Test your rules with LLM tools to ensure they work effectively
- Submit a Pull Request with a clear description of your additions
- Follow the existing documentation format
- Include practical code examples
- Focus on WordPress-specific patterns and conventions
- Ensure rules are actionable and specific
- Test with multiple LLM tools when possible