WordPress
- 44 skills
- 0 followers
- 2.4k repo stars
- last month last updated
- ▌ Self Review 3 · wordpressReview the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.
- ▌ Self Review 4 · wordpressReview the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.
- ▌ Self Review 2 · wordpressReview the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.
- ▌ Wp Bench Execution Tests · wordpressAdd, revise, or review WP-Bench WordPress execution tests. Use when working on datasets/suites/*/execution JSON, runtime_checks, static_checks, reference_solution, reference_files, exploit_solutions, expected_behavior, test ID filtering, WordPress API benchmark coverage, or PR review comments about execution test quality.
- ▌ Self Review · wordpressReview the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.
- ▌ Unit Tests · wordpress bundleTest quality auditor that reviews existing test suites—audits, deletes, rewrites, and fills genuine gaps. Use when asked to review tests, improve test quality, or audit a test suite. Does NOT blindly add tests.
- ▌ Commit Message · wordpress bundleGenerate a WordPress Core Subversion commit message from a GitHub pull request and its linked Trac ticket.
- ▌ Wp 71 Dev Note Issues · wordpressCreate 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.
- ▌ Wp 71 Release Metadata · wordpressPopulate 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 Pr · wordpressEnd-to-end workflow for shipping a non-trivial feature or fix as a pull request in this repo — plan and get sign-off, implement, verify with PHPUnit/phpcs/build, verify manually in a real browser session, open a draft PR with a structured description, and triage/respond to review comments. Use when asked to implement something and open a PR, or to "ship" a change end-to-end.
- ▌ Groups Gatherpress Compat Test · wordpressRun the Groups/GatherPress front-end integration compatibility checklist — per-role browser pass, direct REST pass, GatherPress-off pass, and security/perf sanity checks. Use after any GatherPress version bump, or any change to mu-plugins/wporg-groups-frontend, mu-plugins/groups, or the groups-site theme.
- ▌ Wordcamp Event Recap · wordpress bundleDraft 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.
- ▌ Wordpress News Writing · wordpress bundleDraft 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.
- ▌ Wordpress Social Writer · wordpress bundleGenerate 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.
- ▌ Wordpress Showcase Writer · wordpress bundleWrite 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.
- ▌ Doc Screenshots · wordpress bundleAnnotate UI screenshots with documentation callouts in Fellyph's established visual style — uniform-width orange arrows with white halos, double-stroke target outlines, numbered callout cards, dim overlays and a framed canvas. Use this whenever the user asks to annotate a screenshot, add arrows or callouts to a screenshot, create documentation images, highlight UI controls in a capture, or produce docs/tutorial visuals for Playground, Studio or any web UI — even if they just say "add arrows to this" or "make a docs screenshot".
- ▌ Compile PHP Wasm · wordpressCompile 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 · wordpressDebug 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 PHP Wasm Side Modules · wordpressDebug 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.
- ▌ Playground Website Debugging · wordpressDebug 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.
- ▌ Package Runtime Compatibility · wordpressUse when changing or reviewing a published package across independently updated package and WordPress versions, including API, dependency, entrypoint, registration, allowlist, opt-in, and compatibility changes.
- ▌ Testing · wordpress bundleUse when writing, running, or debugging tests in the Gutenberg repository — JavaScript unit tests (Jest), PHP tests (PHPUnit), or end-to-end tests (Playwright).
- ▌ Defensive Data Design · wordpressUse when adding or changing a user-facing error message or notice, a destructive or irreversible action, or code that reads data it did not create (REST responses, block attributes, post meta, theme.json, localStorage).
- ▌ Design System UI Review · wordpressUse when reviewing a Gutenberg, plugin, or application UI/UX change for correct public WordPress Design System usage and user-facing behaviour, including a component, control, visual styling, token, interaction, layout, overlay, or other user-facing interface; do not use to implement a change or review Design System package source.
- ▌ Emotion To Scss Modules · wordpressUse when planning or implementing an Emotion-to-SCSS-Modules migration in @wordpress/components, including styled wrappers, css/useCx composition, and migration-related cascade fixes.
- ▌ Design System Code Review · wordpressUse when reviewing a Gutenberg change to a WordPress Design System package or its public contract, including `@wordpress/components`, `@wordpress/ui`, or `@wordpress/theme`; do not use to implement the change or review a consumer-only application.
- ▌ Design System Contribution · wordpressUse when planning or implementing a safe `@wordpress/components`, `@wordpress/ui`, or `@wordpress/theme` change in a local Gutenberg checkout; do not use for consumer-only application changes or infer commit, push, or pull-request authority.
- ▌ Design System UI Composition · wordpressUse when building or changing a Gutenberg feature, plugin interface, or standalone application UI with public `@wordpress/components`, `@wordpress/ui`, or `@wordpress/theme` APIs, including when the code does not yet use the Design System; do not use to change package source or depend on package-private implementation details.
- ▌ Wp Patterns · wordpress bundlePattern: create or update WordPress block patterns (starter pages, templates, template parts, Query Loop layouts), review pattern registration, block markup, categories, accessibility, or i18n/escaping, or improve pattern design quality. Route custom blocks to wp-block-development; route frontend interactivity to wp-interactivity-api.
- ▌ Wp REST API · wordpress bundleUse when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
- ▌ Wp Phpstan · wordpress bundleUse when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
- ▌ Blueprint · wordpressUse when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
- ▌ Wp Plugin Development · wordpress bundleUse when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
- ▌ Wp Block Development · wordpress bundleUse 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.
- ▌ Wp Interactivity API · wordpress bundleUse when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
- ▌ Wp Abilities Verify · wordpress bundleVerify 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.
- ▌ Wp Abilities Audit · wordpress bundleAudit 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.
- ▌ Wp Project Triage · wordpress bundleUse when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
- ▌ Wordpress Router · wordpress bundleUse 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).
- ▌ Wp Abilities API · wordpress bundleUse 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.
- ▌ Wp Wpcli And Ops · wordpress bundleUse when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
- ▌ Wp Block Themes · wordpress bundleUse 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).
- ▌ Wp Performance · wordpress bundleUse when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
- ▌ Wp Playground · wordpress bundleUse as the WordPress Playground routing wrapper for ambiguous Playground work, local CLI runs with @wp-playground/cli, playground.wordpress.net share links, browser previews, snapshots, mounts, version switching, and Xdebug. For Blueprint JSON authoring or review, use the blueprint skill directly.