Use when a WordPress admin panel needs real browser interaction via Chrome DevTools MCP — logging in, navigating admin menus, clicking buttons, filling and submitting forms, creating/editing/deleting content through the UI, creating a temporary test admin user, verifying JS state or localStorage, capturing screenshots, or obtaining a REST nonce via admin-ajax.php. Triggers: \"open WP admin\", \"log in to WordPress\", \"navigate to Settings\", \"create a test user in admin\", \"click Save Changes\", \"fill in this form in the browser\", \"take a screenshot of the admin page\", \"upload media through the browser\", \"check the admin menu\", \"verify this in the browser\", \"use Chrome DevTools MCP\", \"fill_form in admin\", \"evaluate_script in admin\", \"admin panel is in maintenance mode\", \"get a REST nonce\", \"session expired re-login\", \"interact with the WP dashboard\", \"navigate to Plugins Add New\", \"test this in the actual admin UI\", \"create a temp admin account for testing\", \"check localStorage in admin\". Not for: headless automated testing without a browser — use wp-plugin-testing; PHP code changes that do not require browser interaction.
$npx -y skills add mralaminahamed/wp-dev-skills --skill wp-admin-browserInstalls into the current project.
Run `npx skills use "https://github.com/mralaminahamed/wp-dev-skills" --skill "mralaminahamed/wp-dev-skills/wp-admin-browser"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/mralaminahamed/wp-dev-skills" that are relevant to the current task. Run `npx skills add "https://github.com/mralaminahamed/wp-dev-skills"` and select the relevant skills, then follow their instructions.