wp-admin-browser
Installation
SKILL.md
WordPress Admin via Browser (Chrome DevTools MCP)
Model note: Primarily MCP tool calls — navigate, fill, click.
haikuworks for simple CRUD flows. Complex UI sequences (multi-step forms, dynamic AJAX state) usesonnetto handle unexpected DOM states.
When to use
- "Log in to the WordPress admin", "navigate to Settings > General", "create a test user".
- "Submit a form in WP admin", "upload a file via the media library", "save plugin settings".
- "Create a temporary admin account for testing instead of using the main admin user".
- "Verify a feature works end-to-end through the browser UI".
Not for: Headless automated testing without a real browser — use wp-plugin-testing. PHP code changes and plugin logic that don't require browser interaction.
Core Rules — Non-Negotiable
- Never touch the main admin user. Always create a temporary admin for testing.
- All data operations go through the browser UI. No WP-CLI, no direct DB, no REST API calls to mutate data — use WordPress forms.
- Navigate via menus, not hardcoded URLs. Click the menu item; don't jump straight to
/wp-admin/users.php?action=.... - Use
fill_form+ click for all inputs. Never skip the form and post directly.