Open
Conversation
Two new skills for developing and debugging in WordPress Studio: studio — Covers site creation, WP-CLI via Studio's bundled PHP, SQLite database access, plugin/theme symlink workflows, Playwright E2E testing, and environment troubleshooting. Includes defensive checks for common conflicts: port collisions, stale /etc/hosts entries, global WP-CLI configs, and rogue processes on development ports. studio-xdebug — Covers Xdebug step debugging in Studio's WASM PHP environment: VS Code launch.json with /wordpress/ path mappings, reading enhanced stack traces, diagnostic mu-plugins, and resolving port 9003 contention. Documents Studio-specific behaviors (appdata-v1.json trust over wp-config.php, single-site Xdebug constraint, WASM internal paths). Both skills include agents/ configs (Claude and OpenAI) and references/ with canonical source links. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The CI runner (eval/harness/run.mjs) requires a 'compatibility' field in each SKILL.md frontmatter. Both studio and studio-xdebug were missing it. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Corrections and additions based on actual Studio + Local coexistence testing: - Fix site path: ~/Studio/<site-name>/, not ~/Library/Application Support/ - Document appdata-v1.json as authoritative config: customDomain and enableHttps override wp-config.php and database at WASM bootstrap - Document that appdata changes require full Studio quit/reopen - Document custom domain conflicts with other web servers on ports 80/443 - Expand troubleshooting checklist with HTTPS redirect loop, custom domain routing, and appdata-specific debugging steps - Remove redundant Xdebug section (defers to studio-xdebug skill) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two new skills for developing and debugging in WordPress Studio developed with Claude Code:
studio— Working in Studio day-to-day: site creation, WP-CLI access via Studio's bundled PHP, SQLite database queries, plugin/theme symlink development, Playwright E2E testing, and environment troubleshooting (port conflicts, stale DNS entries, competing global configs).studio-xdebug— Xdebug step debugging in Studio's WASM PHP environment: VS Codelaunch.jsonwith/wordpress/path mappings, reading enhanced stack traces fromdebug.logand HTTP responses, temporary diagnostic mu-plugins, and resolving port 9003 contention.Why these are separate skills
Not all Studio users will use Xdebug, and Studio's Xdebug behavior is different enough from general Studio usage to warrant a dedicated skill for those who do use it.
Studio runs WASM PHP (not native), uses
/wordpress/as its internal document root, injectsWP_DEBUGconstants at the WASM bootstrap (not wp-config.php), and only allows one site to have Xdebug active at a time. These details are relevant when debugging but clutter the general Studio workflow.What they cover
studio:
~/Library/Application Support/com.wordpress.studio//Applications/WordPress Studio.app/Contents/Resources/wp-cli.pharreuseExistingServer/etc/hostsentry cleanup~/.wp-cli/config.ymlconflict detectionstudio-xdebug:
launch.jsontemplate with WASM path mappingsdebug.logand HTTP responsesappdata-v1.jsontrust model (Studio overrides wp-config.php)conf.d/Test plan
studio/SKILL.mdcovers the standard Studio workflow without referencing other dev environment toolsstudio-xdebug/SKILL.mdpath mappings use/wordpress/(WASM internal root)SKILL.md,agents/,references/)studioskillstudio-xdebugskill