Dulus
An AI agent for your desktop and terminal, on any model you choose. Hosted models run on Fuel, paid in $DULUS.
翻訳待ち
Expert-level WordPress knowledge for AI coding assistants - blocks, themes, plugins, and best practices
翻訳待ち
その他JavaScriptGitHub @WordPress自分でインストール所有者未確認
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗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)
AI coding assistants are powerful, but they often:
Agent Skills solve this by giving AI assistants expert-level WordPress knowledge in a format they can actually use.
| 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-ability-development | Design and review ability schemas, CRUD behavior, and permissions |
| 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 routing, CLI runs, browser previews, and snapshots |
| wpds | WordPress Design System |
| wp-plugin-directory-guidelines | WordPress Plugin Directory Guidelines |
| blueprint | WordPress Playground Blueprints for declarative environment setup |
| wp-env | Local WordPress development with @wordpress/env: setup, configuration, WP-CLI, Xdebug, troubleshooting |
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.
Skills can be installed in two scopes:
Global — installed in your home directory (e.g. ~/.claude/skills/, ~/.cursor/skills/).
Project — installed inside a repository (e.g. .claude/skills/, .github/skills/, .cursor/skills/).
You can use both at the same time. When a skill exists in both scopes, the project-level version is used.
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
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:
npx skills add WordPress/agent-skills --skill wp-plugin-development --global
# Clone agent-skills
git clone https://github.com/WordPress/agent-skills.git
cd agent-skills
# Build the distribution
node shared/scripts/skillpack-build.mjs --clean
# Install all skills globally (available across all projects)
node shared/scripts/skillpack-install.mjs --global
# Or install specific skills only
node shared/scripts/skillpack-install.mjs --global --skills=wp-playground,wp-block-development
This installs skills to ~/.claude/skills/ where Claude Code will automatically discover them.
This is the beginning of the README. Read the rest at the original. Read the full README ↗