wordpress-agent-skills-9

Agent Skills for WordPress

Teach AI coding assistants how to build WordPress the right way.

Agent Skills are portable bundles of instructions, checklists, and scripts that help AI assistants (Claude, Copilot, Codex, Cursor, etc.) understand WordPress development patterns, avoid common mistakes, and follow best practices.

AI Authorship Disclosure: These skills were generated using GPT-5.2 Codex (High Reasoning) from official Gutenberg and WordPress documentation, then reviewed and edited by WordPress contributors. We tested skills with AI assistants and iterated based on results. This is v1, and skills will improve as the community uses them and contributes fixes. See docs/ai-authorship.md for details. (WordPress AI Guidelines)

Why Agent Skills?

AI coding assistants are powerful, but they often:

• Generate outdated WordPress patterns (pre-Gutenberg, pre-block themes)
• Miss critical security considerations in plugin development
• Skip proper block deprecations, causing "Invalid block" errors
• Ignore existing tooling in your repo

Agent Skills solve this by giving AI assistants expert-level WordPress knowledge in a format they can actually use.

Available Skills

Skill	What it teaches
wordpress-router	Classifies WordPress repos and routes to the right workflow
wp-project-triage	Detects project type, tooling, and versions automatically
wp-block-development	Gutenberg blocks: block.json, attributes, rendering, deprecations
wp-block-themes	Block themes: theme.json, templates, patterns, style variations
wp-plugin-development	Plugin architecture, hooks, settings API, security
wp-rest-api	REST API routes/endpoints, schema, auth, and response shaping
wp-interactivity-api	Frontend interactivity with data-wp-* directives and stores
wp-abilities-api	Capability-based permissions and REST API authentication
wp-abilities-audit	Audit a plugin's REST surface and propose Abilities API registrations
wp-abilities-verify	Verify a plugin's Abilities API registrations against their declared annotations
wp-wpcli-and-ops	WP-CLI commands, automation, multisite, search-replace
wp-performance	Profiling, caching, database optimization, Server-Timing
wp-phpstan	PHPStan static analysis for WordPress projects (config, baselines, WP-specific typing)
wp-playground	WordPress Playground for instant local environments
wpds	WordPress Design System
wp-plugin-directory-guidelines	WordPress Plugin Directory Guidelines
blueprint	WordPress Playground Blueprints for declarative Playground environment setup

How It Works

Each skill is a self-contained folder with instructions, references, and optional scripts:

skills/wp-block-development/
├── SKILL.md              # Main instructions (when to use, procedure, verification)
├── references/           # Deep-dive docs on specific topics
│   ├── block-json.md
│   ├── deprecations.md
│   └── ...
└── scripts/              # Deterministic helpers (detection, validation)
    └── list_blocks.mjs

When you ask your AI assistant to work on WordPress code, it reads these skills and follows the documented procedures rather than guessing.

Global vs. Project Scope

Skills can be installed in two scopes:

Global — installed in your home directory (e.g. ~/.claude/skills/, ~/.cursor/skills/).

• Available across all your projects automatically.
• Best for individual developers who want WordPress knowledge in every repo.

Project — installed inside a repository (e.g. .claude/skills/, .github/skills/, .cursor/skills/).

• Available only within that specific project.
• Can be committed to version control so the entire team benefits.

You can use both at the same time. When a skill exists in both scopes, the project-level version is used.

Quick Start

The fastest way to install a skill is with a single command:

npx skills add WordPress/agent-skills --skill wp-plugin-development

To see all available skills:

npx skills add WordPress/agent-skills --list

To install multiple skills at once:

npx skills add WordPress/agent-skills --skill wp-plugin-development wp-abilities-api wp-playground

Choosing a scope

npx skills add asks to choose the skill project-scoped, selecting the local scope on which the skills are installed in the local project; it can be stored at the repository (e.g. .claude/skills/, .cursor/skills/) — so the skills can be committed to version control and shared with your team.

Installing globally makes the skill available to your user (across all your projects). Adding the -g / --global flag, it will install your skill with global scope: