# 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.

- Skill: `jorgerosal/wp-plugin-development` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jorgerosal/wp-plugin-development`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jorgerosal/wp-plugin-development/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: jorgerosal (https://skillmd.com/u/jorgerosal)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jorgerosal/wp-plugin-development

---


# 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