wp-plugin-development
/wp-plugin-development
WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.
- Author
- jorgerosal ↗
- Repository
- wordpress-skills ↗
- Licence
- MIT
- Last repository change
- 07.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.
Original author description
WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.
How it works
- Purpose
- Focus Areas
- Workflow
- Reference Files
- Output
SKILL.md preview
--- name: wp-plugin-development description: WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness. --- # Codex WordPress Plugin Development Review ## Purpose Use this skill when Codex needs to review the architecture and standards of a WordPress plugin rather than only its security or performance characteristics. ## Focus Areas - Main plugin file and header quality - Activation, deactivation, and uninstall flows - Namespacing, prefixing, and collision avoidance - Settings API, CPT, taxonomy, and REST registrations - Hook placement, plugin structure, and i18n - WordPress.org and Plugin Check readiness ## Workflow 1. Detect the plugin context: WordPress.org, private plugin, mu-plugin, or drop-in. 2. Review the main bootstrap file, structure, and lifecycle hooks first. 3. Check CPTs, taxonomies, settings, REST routes, and i18n patterns. 4. Use shared reference docs only where deeper detail is needed. 5. Report findings with severity, file references, architectural impact, and suggested fixes. ## Reference Files Load only the references you need from: - `../../claude-skills/wp-plugin-development/references/architecture-patterns.md` - `../../claude-skills/wp-plugin-development/references/api-patterns.md` - `../../claude-skills/wp-plugin-development/references/hooks-guide.md` - `../../claude-skills/wp-plugin-development/references/oop-patterns.md` ## Output - Group findings by severity - Include file references and plugin-context notes where relevant - Distinguish review blockers from modernization suggestions - Suggest fixes that fit common WordPress plugin conventions
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jorgerosal/wordpress-skills | 90 | MIT |
| pleaseai/claude-code-plugins | 100 | MIT |
| jorgerosal/wordpress-skills | 91 | MIT |
Database snapshot: 13.11.2026 · package version 795268647a16 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100wordpress
WordPress framework guardrails, patterns, and best practices for AI-assisted development. Use when working with WordPress projects, or when the user mentions WordPress. Provides theme development, plugin architecture, REST API, blocks, and security guidelines. - 100wordpress-plugin-core
WordPress plugin development with hooks, security, REST API, custom post types. Use for plugin creation, $wpdb queries, Settings API, or encountering SQL injection, XSS, CSRF, nonce errors. - 100wordpress-wp-plugin-development
Use 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. - 90wordpress-rest-api
Use when talking to a WordPress site over REST: read or write posts, pages, media, users, taxonomy, settings. - 100wp-plugin-rewrite-rules
Design and review custom WordPress URL rewrites: add_rewrite_rule, add_rewrite_tag, query_vars, CPT/taxonomy rewrite slugs, add_rewrite_endpoint, soft vs hard flushes, rewrite_rules cache behavior, and the rule that flush_rewrite_rules() must not run on every request. Use for… - 100wordpress-wp-env
Use when setting up, configuring, or troubleshooting local WordPress development environments with @wordpress/env (wp-env). Triggers on mentions of wp-env, local WordPress development, Docker-based WordPress, or requests to start/stop/configure a local WordPress instance.