WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
WordPress admin UI review and development guidance. An agent skill from jorgerosal/wordpress-skills.
MITAuto-check passed
Install Wp Admin UI Development
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .claude/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .claude/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .agents/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .agents/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .cursor/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .cursor/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jorgerosal/wordpress-skills.git --path claude-skills/wp-admin-ui-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .gemini/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .gemini/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .github/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .github/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jorgerosal/wordpress-skills wp-admin-ui-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-skills/wp-admin-ui-development .opencode/skills/wp-admin-ui-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wp-admin-ui-development" agent skill from https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-admin-ui-development into .opencode/skills/wp-admin-ui-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-admin-ui-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wp-admin-ui-development- GitHub stars
- 100
- Token cost
- ~1.2k tokens
- SKILL.md length
- 408 words
- Files
- 3 (incl. references)
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
WordPress admin UI review and development guidance. An agent skill from jorgerosal/wordpress-skills.
- Works in 5 steps: Identify admin surface → Review screen registration → Review form and state flow → …
- Reviewing admin pages
- SKILL.md covers Overview, When to Use, Code Review Workflow and File-Type Specific Checks, plus 3 more sections
- Calls rg
What it does
Wp Admin UI Development is an agent skill from jorgerosal/wordpress-skills. WordPress admin UI review and development guidance. Use when reviewing admin pages, settings screens, menu pages, notices, list tables, metabox-like interfaces, screen options, capability checks, admin scripts or styles, or when user mentions "admin UI", "settings page", "wp-admin", "admin screen", "options page", "list table", "admin menu", "admin notice", "screen options", or "dashboard page". Detects capability issues, Settings API misuse, admin-only performance problems, and UX mistakes in WordPress admin…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/admin-ux-patterns.md` and `references/settings-and-screens.md`).
It works with WordPress. The repository describes itself as: ✅ 🎉 Claude skills and Codex skills for Wordpress development❗️. The licence is MIT.
When your agent uses it
- Reviewing admin pages
- Settings screens
- Metabox-like interfaces
- Capability checks
Example prompts
- “admin UI”
- “settings page”
- “wp-admin”
- “/wp-admin-ui-development”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify admin surface
- Review screen registration
- Review form and state flow
- Review UX and maintainability
- Apply severity
What it can do on your machine
Read from SKILL.md and the folder at commit 8c96442. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
rg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wp Admin UI Development loads about 1.2k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 138 tokens; SKILL.md has 408 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jorgerosal/wordpress-skills at commit 8c96442, republished under its MIT licence (© jorgerosal). 408 words, ~1,166 tokens.
Download SKILL.mdSave it as
.claude/skills/wp-admin-ui-development/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- wp-admin-ui-development
- description
- WordPress admin UI review and development guidance. Use when reviewing admin pages, settings screens, menu pages, notices, list tables, metabox-like interfaces, screen options, capability checks, admin scripts or styles, or when user mentions "admin UI", "settings page", "wp-admin", "admin screen", "options page", "list table", "admin menu", "admin notice", "screen options", or "dashboard page". Detects capability issues, Settings API misuse, admin-only performance problems, and UX mistakes in WordPress admin interfaces.
WordPress Admin UI Development Skill
Overview
Systematic review for WordPress admin interfaces. Core principle: Admin UIs should be capability-aware, predictable, and aligned with WordPress admin patterns instead of custom app-style behavior. Review covers menu registration, screen architecture, Settings API usage, notices, script and style loading, list-table patterns, and admin-side UX stability.
When to Use
Use when:
- Reviewing settings pages or plugin dashboards
- Auditing
add_menu_page()/add_submenu_page()usage - Checking admin forms, notices, and data-entry screens
- Reviewing admin script loading and screen targeting
- Analyzing capability checks for admin pages
Don't use for:
- Frontend UI review
- Full security-only audits (use wp-security-review)
- General plugin architecture without admin surface focus (use wp-plugin-development)
Code Review Workflow
Identify admin surface
- Settings page
- Dashboard widget or tools page
- Custom list table
- Modal-heavy admin workflow
Review screen registration
- Menu slug, parent slug, capability
- Dedicated callbacks
- Screen-specific enqueue logic
Review form and state flow
- Settings API or deliberate alternative
- Nonces and capability checks
- Stable success/error messaging
Review UX and maintainability
- Avoid giant single-screen forms
- Respect WordPress admin layout and component conventions
- Load scripts only on relevant screens
Apply severity
- CRITICAL: Missing capability checks, unrestricted admin actions, admin screens accessible to wrong roles
- WARNING: Global admin asset loading, bypassed Settings API, unstable notice UX, oversized screens
- INFO: Could use core components or cleaner screen split
File-Type Specific Checks
Admin Menu Registration
- CRITICAL: Missing capability requirement
- WARNING: Menu callback mixes routing, rendering, and form handling
- INFO: Could move large screens into separate classes or modules
Show full SKILL.md (161 more words)Show less
Settings Forms
- CRITICAL: Missing nonce or capability check on save
- WARNING: Manual
update_option()everywhere without Settings API structure - WARNING: No sanitization callback for settings
- INFO: Could split settings into sections/tabs for maintainability
Admin Scripts and Styles
- WARNING: Scripts loaded on every admin screen
- WARNING: Inline JS for large features
- INFO: Could use screen IDs and conditional enqueues
Notices and Feedback
- WARNING: Persistent notices without dismissal handling
- WARNING: Success/error states are not tied to actual action outcome
- INFO: Could use clearer empty/loading states
Search Patterns for Quick Detection (ADM-21)
Use these rg commands for quick admin UI scanning.
CRITICAL Patterns
# Admin page registration
rg -n "add_menu_page|add_submenu_page|add_options_page|add_management_page" . -g '*.php'
# Admin-post handlers and nonces
rg -n "admin_post_|check_admin_referer|wp_verify_nonce|current_user_can" . -g '*.php'WARNING Patterns
# Global admin enqueues
rg -n "admin_enqueue_scripts|wp_enqueue_script|wp_enqueue_style" . -g '*.php'
# Direct option updates in admin pages
rg -n "update_option|add_option" . -g '*.php'
# Admin notices
rg -n "admin_notices|notice-|is-dismissible" . -g '*.php'INFO Patterns
# Settings API usage
rg -n "register_setting|add_settings_section|add_settings_field" . -g '*.php'
# Screen targeting helpers
rg -n "get_current_screen|current_screen|\$hook_suffix" . -g '*.php'Reference Files
references/settings-and-screens.md- Settings pages, screen registration, and admin screen structurereferences/admin-ux-patterns.md- Notices, admin scripts, tabs, list tables, and UX expectations
Output Format (ADM-23)
For each finding include severity, file reference, issue summary, admin impact, and a concrete fix suggestion. Call out where a problem is primarily security, architecture, or UX so follow-up reviews are easy to route.
© jorgerosal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in claude-skills/wp-admin-ui-development of jorgerosal/wordpress-skills.
- SKILL.md
- references/admin-ux-patterns.md
- references/settings-and-screens.md
Open the folder on GitHubat commit 8c96442
Compare with similar skills
Wp Admin UI Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wp Admin UI Development this skilljorgerosal/wordpress-skills | 100 | — | ~1.2k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Wp Block Developmentgambitph/Stackable | 350 | 3 repos | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| Postizgitroomhq/postiz-agent | 505 | 2 repos | ~7.9k | Automated safety check: Pass | AGPL-3.0 | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 234 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Wp Interactivity APIAutomattic/agent-skills | 211 | 2 repos | ~1.5k | Automated safety check: Pass | None |
Similar skills
Wp Block Development
gambitph/Stackable
A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…
Postiz
gitroomhq/postiz-agent
Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest…
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
Wp Interactivity API
Automattic/agent-skills
A skill your agent uses when building or debugging WordPress Interactivity API features (data-wp- directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration…
Wp Env
WordPress/agent-skills
A skill your agent uses when setting up, configuring, or troubleshooting local WordPress development environments with @wordpress/env (wp-env).
More from jorgerosal/wordpress-skills
All 35 skills in this repoWp Accessibility Review
jorgerosal/wordpress-skills
WordPress accessibility review for themes, blocks, plugins, and admin interfaces.
Wp Acf And Content Modeling
jorgerosal/wordpress-skills
WordPress ACF and content modeling review. An agent skill from jorgerosal/wordpress-skills.
Wp CI CD And Release Engineering
jorgerosal/wordpress-skills
WordPress CI/CD and release engineering review guidance. An agent skill from jorgerosal/wordpress-skills.
Wp Headless And Wpgraphql
jorgerosal/wordpress-skills
Headless WordPress and WPGraphQL review guidance. An agent skill from jorgerosal/wordpress-skills.
Wp Migration Upgrade Review
jorgerosal/wordpress-skills
WordPress migration and upgrade review. An agent skill from jorgerosal/wordpress-skills.
Wp Phpstan Review
jorgerosal/wordpress-skills
WordPress PHPStan review and setup guidance. An agent skill from jorgerosal/wordpress-skills.
Related
Works with
Questions about Wp Admin UI Development
What does Wp Admin UI Development do?
WordPress admin UI review and development guidance. An agent skill from jorgerosal/wordpress-skills. Wp Admin UI Development is an agent skill from jorgerosal/wordpress-skills. WordPress admin UI review and development guidance.
When should I use Wp Admin UI Development?
Wp Admin UI Development fits situations like: reviewing admin pages; settings screens; metabox-like interfaces; capability checks.
How do I install Wp Admin UI Development in Claude Code?
Run `npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a claude-code`. Or copy the skill folder (claude-skills/wp-admin-ui-development in jorgerosal/wordpress-skills) into .claude/skills/wp-admin-ui-development in your project. Claude Code loads it when a task matches its description.
How do I install Wp Admin UI Development in Codex?
Run `npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a codex`. Or copy the skill folder (claude-skills/wp-admin-ui-development in jorgerosal/wordpress-skills) into .agents/skills/wp-admin-ui-development in your project. Codex loads it when a task matches its description.
Can I use Wp Admin UI Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jorgerosal/wordpress-skills --skill wp-admin-ui-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-admin-ui-development, .gemini/skills/wp-admin-ui-development, .github/skills/wp-admin-ui-development and .opencode/skills/wp-admin-ui-development in your project.
What does Wp Admin UI Development need to run?
Going by SKILL.md and its folder, Wp Admin UI Development needs the command-line tools its instructions call (rg).
Does Wp Admin UI Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wp Admin UI Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wp Admin UI Development use?
Wp Admin UI Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wp Admin UI Development use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 263 tokens, read only when the agent opens those files.
What are the alternatives to Wp Admin UI Development?
Skills that share tags, products or a category with Wp Admin UI Development: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Wp Block Development (gambitph/Stackable, 350 stars), Postiz (gitroomhq/postiz-agent, 505 stars) and Wp Performance Review (elvismdev/claude-wordpress-skills, 234 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wp Admin UI Development?
jorgerosal (a GitHub user) maintains it in jorgerosal/wordpress-skills, which has 100 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on June 7, 2026.
Source: jorgerosal/wordpress-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.