WordPress

Generate technically correct, design-distinctive WordPress block patterns. Use when creating block patterns, starter page patterns, template patterns, template part patterns, or improving pattern design quality. Covers pattern registration (PHP headers, auto/manual), block markup syntax, theme.json design tokens, categories, template types, accessibility, and i18n/escaping.

Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).

Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.

Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.

Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.

Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).

Compile PHP.wasm main modules and side modules (dynamic extensions) for Node.js and web platforms. Use when recompiling PHP, adding Emscripten flags, modifying Dockerfiles, building extensions as SIDE_MODULE, upgrading Emscripten, or troubleshooting compilation failures.

Debug PHP.wasm main module crashes including Asyncify errors (unreachable, memory access out of bounds), JSPI errors (SuspendError, trying to suspend JS frames), WASM memory growth bugs, and runtime traps. Use when investigating RuntimeError, null function or signature mismatch, or other WASM-related crashes in the main PHP binary.

Debug WASM side modules (dynamic PHP extensions) including dlopen failures, SIDE_MODULE loading, JSPI suspension crashes in extensions, C++ weak symbol issues, and extension runtime errors. Use when working with dynamic extensions like Xdebug, intl, or GD built as WASM side modules.

Debug the WordPress Playground website by running the dev server from source and interacting with it via Playwright MCP. Use when investigating UI bugs, testing website features, checking for JavaScript errors, debugging hanging requests, or verifying WordPress behavior in the browser-based Playground.

Write two-paragraph website descriptions for the WordPress Showcase (wordpress.org/showcase) in the voice of the WordPress open source project. Use when drafting or revising a Showcase entry from a submitted Site URL, a submitter Description, and a Reason for Submission, or whenever someone wants an on-brand description of a site built with WordPress that helps demonstrate what the platform can do across personal blogs, small businesses, enterprise companies, and national governments. The first paragraph describes the company, organization, brand, or person behind the site; the second describes how WordPress is used in an interesting or unique way. Applies the WordPress Marketing Style Guide and Brand Book.

Draft posts for WordPress.org/news in the official voice of the WordPress open source project, following the WordPress Marketing Style Guide and Brand Book. Use whenever the user wants to write, draft, ghostwrite, or revise a WordPress.org/news post, a WordPress project announcement, a version release post (major, minor, maintenance, security, beta, or release candidate), a product or feature launch, a WordCamp recap, or any public-facing content that should read as if it comes from the WordPress project. Also use when adapting existing copy into the WordPress.org news voice, or when checking that a draft matches WordPress editorial and terminology conventions.

Generate ready-to-publish social media posts for the WordPress open source project across X, Bluesky, Threads, Mastodon, Facebook, Instagram, LinkedIn, and Tumblr from a single feed item (post title, URL, and content). Use when turning a WordPress.org/news post, developer.wordpress.org/news article, WordPress Showcase entry, WordCamp event page, or other WordPress community link into per-platform social copy in the WordPress project voice. Applies the WordPress Marketing Style Guide, per-platform character limits, approved hashtags, shortlink detection, and tone calibration, and emits one labeled field per platform for downstream automation.

Draft a flagship WordCamp event recap for WordPress.org/news in the Events category, grounded in real event notes and live event sources rather than an AI summary of a schedule. Use when writing, drafting, building, or revising a recap of a WordCamp such as WordCamp US, WordCamp Europe, WordCamp Asia, or another flagship regional WordCamp, including coverage of Contributor Day, opening and closing keynotes, sessions and tracks, sponsors, photo galleries, human texture, and next-event calls to action. Builds on the wordpress-news-writing skill and adds event-recap-specific input requirements, a required source-gathering pass, post structure, tone and humanizer rules, and a final self-edit checklist.

Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json. Use when asked to build, update, synchronize, reconcile, or validate WordPress 7.1 release metadata from the local component files.

Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker. Use when asked to import, sync, or create GitHub issues for triaged WordPress 7.1 Trac tickets.

Add, revise, or review WP-Bench WordPress execution tests. Use when working on datasets/suites/*/execution JSON, runtime_checks, static_checks, reference_solution, expected_behavior, test ID filtering, WordPress API benchmark coverage, or PR review comments about execution test quality.

Navigate and understand the MCP PHP schema. Use when implementing MCP clients/servers, understanding protocol types, or finding the right DTO for a task.