Skip to content
Back to search

wordpress-skills

βœ… πŸŽ‰ Claude skills and Codex skills for Wordpress development❗️

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jorgerosal--wordpress-skills/badge.svg)](/listings/jorgerosal--wordpress-skills)

HTML

<a href="/listings/jorgerosal--wordpress-skills"><img src="/api/listings/jorgerosal--wordpress-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Choose the install path for the agent you want to use.

Claude Code

Which Option Should You Use?

- **Use Option 1** if you want the skills available inside one project for yourself or your team - **Use Option 2** if you want the skills available across your machine - **Use Option 3** if you only want one Claude skill and are fine updating it manually

Option 1: Add to Your Project (Recommended)

Best for shared projects, client work, and teams.

# In your project root
git submodule add https://github.com/jorgerosal/wordpress-skills.git .claude/plugins/wordpress-skills
git commit -m "Add WordPress Claude skills"

To update later:

git submodule update --remote .claude/plugins/wordpress-skills
git add .claude/plugins/wordpress-skills
git commit -m "Update WordPress Claude skills"

Option 2: Install for Your User Account

Best for solo usage across multiple projects.

git clone https://github.com/jorgerosal/wordpress-skills.git ~/.claude/plugins/wordpress-skills

To update later:

cd ~/.claude/plugins/wordpress-skills
git pull

Option 3: Install One Skill Manually

Best if you only want a single skill and do not need the full pack.

# Copy just the performance review skill
cp -r claude-skills/wp-performance-review ~/.claude/skills/

If you use this option, updates are manual. Re-copy the skill when the source changes.

Verify the Claude Install

After installing:

1. Restart Claude Code if needed 2. Open a WordPress project 3. Run a namespaced plugin command such as:

/wordpress-skills:wp-perf-review

The plugin install paths above use Claude Code's plugin loader, so commands are namespaced with the plugin name (`wordpress-skills`). If you manually copy a skill into `~/.claude/skills/`, the command stays unnamespaced.

Codex

Install the parallel Codex wrappers if you want the same WordPress domains available as Codex skills.

Option 1: Install All Codex Skills

mkdir -p ~/.codex/skills
cp -r codex-skills/* ~/.codex/skills/
cp -r claude-skills ~/.codex/claude-skills

Option 2: Install One Codex Skill

mkdir -p ~/.codex/skills
cp -r codex-skills/wp-performance-review ~/.codex/skills/
mkdir -p ~/.codex/claude-skills/wp-performance-review
cp -r claude-skills/wp-performance-review/references ~/.codex/claude-skills/wp-performance-review/

If your Codex setup uses a custom `CODEX_HOME`, copy the wrappers into `$CODEX_HOME/skills/` and the shared reference tree into `$CODEX_HOME/claude-skills/`.

Verify the Codex Install

Open a WordPress project in Codex and invoke the skill naturally, for example:

Review this plugin for performance issues

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md Β· README Β· 458 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # WordPress Skills for Claude and Codex
  2. <p align="center">
  3. <img src="public/Claude%20Skills%20for%20Wordpress.jpg" alt="WordPress Skills for Claude and Codex" width="100%" />
  4. </p>
  5. <p align="center">
  6. <a href="https://claude.ai/code">
  7. <img src="https://img.shields.io/badge/Claude%20Code-Ready-1f6feb?style=for-the-badge" alt="Claude Code Ready" />
  8. </a>
  9. <img src="https://img.shields.io/badge/Codex-Parallel%20skills-0a7ea4?style=for-the-badge" alt="Codex parallel skills" />
  10. <img src="https://img.shields.io/badge/WordPress-18%20review%20domains-21759b?style=for-the-badge&logo=wordpress&logoColor=white" alt="WordPress review domains" />
  11. <img src="https://img.shields.io/badge/Commands-36%20slash%20commands-2da44e?style=for-the-badge" alt="36 slash commands" />
  12. <img src="https://img.shields.io/badge/Focus-Code%20review%20and%20triage-8250df?style=for-the-badge" alt="Code review and triage" />
  13. </p>
  14. Professional WordPress skills for [Claude Code](https://claude.ai/code) and Codex, built for AI-assisted WordPress code review, fast triage, onboarding, and modern WordPress development workflows across plugin architecture, security audits, ACF/content modeling, headless WPGraphQL, blocks, themes, WooCommerce, REST APIs, admin UI, migrations, accessibility, testing, release engineering, WP-CLI operations, Playground, and PHPStan.
  15. ## Why This Pack
  16. - Structured review workflows for real WordPress codebases
  17. - Fast onboarding for inherited WordPress repositories before deeper review
  18. - Quick triage commands for fast audits before deeper review
  19. - Specialized guidance for Gutenberg, block themes, and WooCommerce
  20. - Cross-skill handoffs when a finding belongs in another domain
  21. - Line-numbered, severity-based review output with fix guidance
  22. - Parallel skill wrappers for both Claude and Codex
  23. ## Repository Layout
  24. ```text
  25. .claude-plugin/ # Claude Code plugin manifest
  26. claude-skills/ # Canonical Claude-oriented skill pack with shared reference docs
  27. skills/ # Claude Code plugin-compatible alias to claude-skills/
  28. codex-skills/ # Codex-oriented skill wrappers for the same seventeen domains
  29. commands/ # Claude slash commands
  30. public/ # README assets
  31. docs/ # GitHub Pages docs and guide surface
  32. ```
  33. The Codex skills reuse the domain references stored under `claude-skills/` so the review heuristics stay aligned without duplicating the whole reference library.
  34. The project also includes a deployable GitHub Pages site in `docs/`.
  35. ## Validation
  36. Run the repository validator before opening a PR or after adding skills, commands, or docs:
  37. ```bash
  38. python3 scripts/validate_repo.py
  39. ```
  40. ## Guides and Workflow Docs
  41. The GitHub Pages docs double as a search-friendly surface for specific WordPress + AI review workflows:
  42. - [Guide index](https://jorgerosal.github.io/wordpress-skills/guides/)
  43. - [How to review a WordPress plugin with Claude Code](https://jorgerosal.github.io/wordpress-skills/guides/review-wordpress-plugin-with-claude-code.html)
  44. - [WordPress AI code review FAQ](https://jorgerosal.github.io/wordpress-skills/guides/wordpress-ai-code-review-faq.html)
  45. - [How to review a WooCommerce plugin with Claude Code](https://jorgerosal.github.io/wordpress-skills/guides/review-woocommerce-plugin-with-claude-code.html)
  46. - [How to review a WordPress REST API with Claude Code](https://jorgerosal.github.io/wordpress-skills/guides/review-wordpress-rest-api-with-claude-code.html)
  47. - [How to review a WooCommerce extension with Claude Code](https://jorgerosal.github.io/wordpress-skills/guides/review-woocommerce-extension-with-claude-code.html)
  48. - [WordPress release engineering checklist for Claude Code](https://jorgerosal.github.io/wordpress-skills/guides/wordpress-release-engineering-checklist.html)
  49. These pages are meant for both human readers and AI/search systems, with concrete commands, checklists, and example findings.
  50. ## Available Skills
  51. `βœ…` Available now Β· `🚧` In progress
  52. | Skill | Focus | Status |
  53. |-------|-------|--------|
  54. | **wp-performance-review** | Performance bottlenecks, query patterns, caching, cron, asset loading | βœ… |
  55. | **wp-security-review** | XSS, SQL injection, CSRF, auth checks, file upload risks | βœ… |
  56. | **wp-plugin-development** | Plugin structure, lifecycle hooks, Settings API, i18n, WordPress.org standards | βœ… |
  57. | **wp-acf-and-content-modeling** | ACF field groups, CPT/taxonomy design, repeaters, flexible content, JSON sync, and meta-query risk | βœ… |
  58. | **wp-headless-and-wpgraphql** | WPGraphQL schema design, preview/auth flows, resolver performance, caching, and frontend revalidation | βœ… |
  59. | **wp-block-development** | `block.json`, React/JSX editor patterns, render callbacks, Interactivity API | βœ… |
  60. | **wp-theme-development** | `theme.json`, templates, template parts, style variations, FSE patterns | βœ… |
  61. | **wp-woocommerce-dev** | HPOS, CRUD APIs, payment gateway patterns, cart fragments, template overrides | βœ… |
  62. | **wp-rest-api-development** | Custom REST routes, permission callbacks, schema design, request validation, response shape | βœ… |
  63. | **wp-admin-ui-development** | Settings pages, admin menus, notices, screen targeting, admin form flows | βœ… |
  64. | **wp-migration-upgrade-review** | Versioned upgrades, `dbDelta()`, backfills, rollout safety, schema changes | βœ… |
  65. | **wp-accessibility-review** | Semantic markup, keyboard access, focus behavior, labels, ARIA, accessible interactions | βœ… |
  66. | **wp-test-strategy** | Unit vs integration vs E2E coverage, test planning, regression risk, WordPress test gaps | βœ… |
  67. | **wp-ci-cd-and-release-engineering** | GitHub Actions, artifact packaging, deploy gating, WordPress.org release flows, and rollback safety | βœ… |
  68. | **wp-site-audit-and-onboarding** | First-pass WordPress codebase classification, stack discovery, risk surfacing, and routing into the right follow-up reviews | βœ… |
  69. | **wp-wpcli-and-ops** | WP-CLI workflows, multisite operations, search-replace safety, automation, and deployment checks | 🚧 |
  70. | **wp-playground-development** | WordPress Playground blueprints, reproducible demos, zero-setup bug repros, and embed patterns | 🚧 |
  71. | **wp-phpstan-review** | PHPStan for WordPress projects, baseline strategy, CI integration, and practical static-analysis review | 🚧 |
  72. ## Installation
  73. Choose the install path for the agent you want to use.
  74. ### Claude Code
  75. #### Which Option Should You Use?
  76. - **Use Option 1** if you want the skills available inside one project for yourself or your team
  77. - **Use Option 2** if you want the skills available across your machine
  78. - **Use Option 3** if you only want one Claude skill and are fine updating it manually
  79. #### Option 1: Add to Your Project (Recommended)
  80. Best for shared projects, client work, and teams.
  81. ```bash
  82. # In your project root
  83. git submodule add https://github.com/jorgerosal/wordpress-skills.git .claude/plugins/wordpress-skills
  84. git commit -m "Add WordPress Claude skills"
  85. ```
  86. To update later:
  87. ```bash
  88. git submodule update --remote .claude/plugins/wordpress-skills
  89. git add .claude/plugins/wordpress-skills
  90. git commit -m "Update WordPress Claude skills"
  91. ```
  92. #### Option 2: Install for Your User Account
  93. Best for solo usage across multiple projects.
  94. ```bash
  95. git clone https://github.com/jorgerosal/wordpress-skills.git ~/.claude/plugins/wordpress-skills
  96. ```
  97. To update later:
  98. ```bash
  99. cd ~/.claude/plugins/wordpress-skills
  100. git pull
  101. ```
  102. #### Option 3: Install One Skill Manually
  103. Best if you only want a single skill and do not need the full pack.
  104. ```bash
  105. # Copy just the performance review skill
  106. cp -r claude-skills/wp-performance-review ~/.claude/skills/
  107. ```
  108. If you use this option, updates are manual. Re-copy the skill when the source changes.
  109. #### Verify the Claude Install
  110. After installing:
  111. 1. Restart Claude Code if needed
  112. 2. Open a WordPress project
  113. 3. Run a namespaced plugin command such as:
  114. ```bash
  115. /wordpress-skills:wp-perf-review
  116. ```
  117. The plugin install paths above use Claude Code's plugin loader, so commands are namespaced with the plugin name (`wordpress-skills`). If you manually copy a skill into `~/.claude/skills/`, the command stays unnamespaced.
  118. ### Codex
  119. Install the parallel Codex wrappers if you want the same WordPress domains available as Codex skills.
  120. #### Option 1: Install All Codex Skills
  121. ```bash
  122. mkdir -p ~/.codex/skills
  123. cp -r codex-skills/* ~/.codex/skills/
  124. cp -r claude-skills ~/.codex/claude-skills
  125. ```
  126. #### Option 2: Install One Codex Skill
  127. ```bash
  128. mkdir -p ~/.codex/skills
  129. cp -r codex-skills/wp-performance-review ~/.codex/skills/
  130. mkdir -p ~/.codex/claude-skills/wp-performance-review
  131. cp -r claude-skills/wp-performance-review/references ~/.codex/claude-skills/wp-performance-review/
  132. ```
  133. If your Codex setup uses a custom `CODEX_HOME`, copy the wrappers into `$CODEX_HOME/skills/` and the shared reference tree into `$CODEX_HOME/claude-skills/`.
  134. #### Verify the Codex Install
  135. Open a WordPress project in Codex and invoke the skill naturally, for example:
  136. ```text
  137. Review this plugin for performance issues
  138. ```
  139. ## Slash Commands
  140. Claude skills include a full review command and a faster triage command.
  141. | Command | Use Case |
  142. |---------|----------|
  143. | `/wp-perf-review [path]` | Full performance review with grouped findings and fix guidance |
  144. | `/wp-perf [path]` | Fast performance scan for critical patterns |
  145. | `/wp-sec-review [path]` | Full security review for exploitable patterns |
  146. | `/wp-sec [path]` | Fast security scan for common high-risk issues |
  147. | `/wp-plugin-review [path]` | Full plugin architecture and standards review |
  148. | `/wp-plugin [path]` | Fast plugin structure and standards scan |
  149. | `/wp-acf-review [path]` | Full ACF and content-modeling review for CPTs, taxonomies, field groups, JSON sync, and meta-query risk |
  150. | `/wp-acf [path]` | Fast ACF/content-model scan for schema and field-group issues |
  151. | `/wp-headless-review [path]` | Full headless WordPress and WPGraphQL review for schema, preview/auth, and cache/build workflows |
  152. | `/wp-headless [path]` | Fast headless/WPGraphQL scan for schema and preview/cache risks |
  153. | `/wp-block-review [path]` | Full Gutenberg block review across PHP and JS/JSX |
  154. | `/wp-block [path]` | Fast block API and `block.json` scan |
  155. | `/wp-theme-review [path]` | Full block or classic theme review |
  156. | `/wp-theme [path]` | Fast theme structure and FSE scan |
  157. | `/wp-woo-review [path]` | Full WooCommerce extension review |
  158. | `/wp-woo [path]` | Fast WooCommerce compatibility and risk scan |
  159. | `/wp-rest-review [path]` | Full REST API review for routes, auth, validation, and response design |
  160. | `/wp-rest [path]` | Fast REST API scan for route and permission issues |
  161. | `/wp-admin-review [path]` | Full admin UI review for settings screens, menus, notices, and admin UX |
  162. | `/wp-admin [path]` | Fast admin UI scan for menus, settings flow, and admin asset loading |
  163. | `/wp-migration-review [path]` | Full migration and upgrade review for versioned updates, schema changes, and backfills |
  164. | `/wp-migration [path]` | Fast migration scan for risky upgrade patterns |
  165. | `/wp-a11y-review [path]` | Full accessibility review for themes, blocks, plugins, and admin interfaces |
  166. | `/wp-a11y [path]` | Fast accessibility scan for semantic, keyboard, focus, and ARIA issues |
  167. | `/wp-test-review [path]` | Full test strategy review with prioritized unit, integration, and E2E recommendations |
  168. | `/wp-test [path]` | Fast testing scan for existing coverage and likely test gaps |
  169. | `/wp-release-review [path]` | Full CI/CD and release engineering review for pipelines, artifacts, gating, and rollback readiness |
  170. | `/wp-release [path]` | Fast CI/CD and release scan for deploy and packaging risks |
  171. | `/wp-onboard-review [path]` | Full WordPress onboarding review for stack classification, architecture mapping, and next-review routing |
  172. | `/wp-onboard [path]` | Fast WordPress onboarding scan for stack detection and initial risk triage |
  173. | `/wp-ops-review [path]` | Full WP-CLI and operations review for custom commands, multisite scope, and maintenance workflows |
  174. | `/wp-ops [path]` | Fast WP-CLI and operational risk scan |
  175. | `/wp-playground-review [path]` | Full Playground review for Blueprints, repro environments, and embed flows |
  176. | `/wp-playground [path]` | Fast Playground scan for Blueprint and repro issues |
  177. | `/wp-phpstan-review [path]` | Full PHPStan review for config, baselines, CI wiring, and WordPress-specific analysis setup |
  178. | `/wp-phpstan [path]` | Fast PHPStan scan for config and static-analysis issues |
  179. ### Quick Examples
  180. ```bash
  181. # Review the current project for performance issues
  182. /wp-perf-review
  183. # Run a fast security scan on a plugin
  184. /wp-sec wp-content/plugins/my-plugin
  185. # Review ACF field groups and content architecture
  186. /wp-acf-review wp-content/themes/my-theme
  187. # Review a headless WPGraphQL stack
  188. /wp-headless-review apps/web
  189. # Review a custom block package
  190. /wp-block-review wp-content/plugins/my-blocks
  191. # Review a block theme
  192. /wp-theme-review wp-content/themes/my-theme
  193. # Check a WooCommerce extension before release
  194. /wp-woo-review wp-content/plugins/my-woo-extension
  195. # Review custom REST API endpoints
  196. /wp-rest-review wp-content/plugins/my-api-plugin
  197. # Plan tests for a risky plugin change
  198. /wp-test-review wp-content/plugins/my-plugin
  199. # Review WordPress release engineering and deployment workflow
  200. /wp-release-review .github/workflows
  201. # Onboard to an inherited WordPress repo before deeper review
  202. /wp-onboard-review .
  203. # Review custom WP-CLI operations and runbooks
  204. /wp-ops-review wp-content/plugins/my-plugin
  205. # Review a WordPress Playground Blueprint or demo setup
  206. /wp-playground-review docs/playground
  207. # Review PHPStan setup for a plugin or theme
  208. /wp-phpstan-review .
  209. ```
  210. When installed as a Claude Code plugin or from the marketplace, commands are namespaced:
  211. ```bash
  212. /wordpress-skills:wp-perf-review [path]
  213. /wordpress-skills:wp-perf [path]
  214. ```
  215. ## Natural Language Usage
  216. You can also invoke the skills without slash commands or explicit command files. Ask naturally, for example:
  217. ```text
  218. Review this plugin for performance issues
  219. Audit this theme for security problems
  220. Help me debug this block.json setup
  221. Check this WooCommerce extension for HPOS issues
  222. Review this theme before launch
  223. Find slow queries in this plugin
  224. Review these custom REST routes
  225. Check this plugin settings page
  226. Audit this release migration before deploy
  227. Onboard me to this WordPress repo and tell me what to review first
  228. Review this WP-CLI command for operational risk
  229. Check this Blueprint for a reliable Playground repro
  230. Audit this phpstan.neon for WordPress plugin analysis
  231. Review this theme for accessibility issues
  232. What tests should I add for this change?
  233. ```
  234. Claude or Codex will match the request to the most relevant skill and follow that review workflow.
  235. ### Trigger Phrases
  236. | Skill | Common Triggers |
  237. |-------|------------------|
  238. | `wp-performance-review` | "performance review", "slow WordPress", "slow queries", "high-traffic", "timeout", "out of memory" |
  239. | `wp-security-review` | "security audit", "XSS", "SQL injection", "CSRF", "nonce verification", "capability check" |
  240. | `wp-plugin-development` | "plugin review", "plugin architecture", "activation hook", "Settings API", "Plugin Check" |
  241. | `wp-acf-and-content-modeling` | "ACF review", "field groups", "flexible content", "content modeling", "ACF JSON" |
  242. | `wp-headless-and-wpgraphql` | "WPGraphQL", "headless WordPress", "preview flow", "resolver", "frontend revalidation" |
  243. | `wp-block-development` | "block review", "Gutenberg", "block.json", "InnerBlocks", "Interactivity API", "dynamic block" |
  244. | `wp-theme-development` | "theme review", "block theme", "theme.json", "FSE", "template parts", "style variations" |
  245. | `wp-woocommerce-dev` | "WooCommerce review", "HPOS", "payment gateway", "cart fragments", "Action Scheduler" |
  246. | `wp-rest-api-development` | "REST API review", "register_rest_route", "permission_callback", "REST endpoint", "API schema" |
  247. | `wp-admin-ui-development` | "admin UI", "settings page", "admin screen", "admin menu", "admin notice" |
  248. | `wp-migration-upgrade-review` | "migration review", "upgrade routine", "dbDelta", "schema change", "backfill" |
  249. | `wp-accessibility-review` | "accessibility review", "a11y", "keyboard navigation", "focus management", "semantic HTML" |
  250. | `wp-test-strategy` | "test strategy", "PHPUnit", "integration tests", "Playwright", "coverage" |
  251. | `wp-ci-cd-and-release-engineering` | "release review", "GitHub Actions", "artifact packaging", "deploy gating", "rollback" |
  252. ## What Each Skill Covers
  253. All shipped and in-progress skills are designed to produce structured findings with severity labels (`Critical`, `Warning`, `Info`), file references, and concrete recommendations.
  254. ### `wp-performance-review`
  255. - Database query anti-patterns
  256. - Expensive hooks and page-load writes
  257. - Object cache and transient usage
  258. - AJAX, HTTP, and polling bottlenecks
  259. - Template-level N+1 patterns
  260. - Asset loading and cron issues
  261. ### `wp-security-review`
  262. - XSS and output escaping issues
  263. - SQL injection risks
  264. - CSRF and nonce validation gaps
  265. - Capability and authorization mistakes
  266. - File upload handling risks
  267. - Dangerous functions and sensitive data exposure
  268. ### `wp-plugin-development`
  269. - Plugin headers and structure
  270. - Activation, deactivation, and uninstall flows
  271. - CPT and taxonomy registration
  272. - Settings API usage
  273. - Hook design and priority issues
  274. - Internationalization and WordPress.org readiness
  275. ### `wp-block-development`
  276. - `block.json` schema validation
  277. - `edit` and `save` function patterns
  278. - Render callbacks and dynamic blocks
  279. - Attribute handling and deprecations
  280. - Interactivity API usage
  281. - Build setup and source/build review
  282. ### `wp-theme-development`
  283. - `theme.json` validation
  284. - Template hierarchy and required files
  285. - Template parts and block markup
  286. - Global styles and spacing systems
  287. - Style variations and patterns
  288. - Classic-to-block migration guidance
  289. ### `wp-woocommerce-dev`
  290. - HPOS compatibility
  291. - WooCommerce CRUD usage
  292. - Payment gateway safety patterns
  293. - Cart fragments and performance concerns
  294. - Action Scheduler usage
  295. - Template override quality and hook preservation
  296. ### `wp-rest-api-development`
  297. - Route registration and namespace design
  298. - `permission_callback` quality
  299. - Request arg validation and sanitization
  300. - Response shape and status codes
  301. - Controller patterns and versioning
  302. ### `wp-admin-ui-development`
  303. - Settings pages and admin menus
  304. - Capability-aware screen access
  305. - Admin notices and save feedback
  306. - Screen-specific asset loading
  307. - Settings API and admin UX structure
  308. ### `wp-migration-upgrade-review`
  309. - Versioned upgrade routines
  310. - Schema changes and `dbDelta()`
  311. - Data backfills and batching
  312. - Upgrade safety and idempotency
  313. - Rollout and rollback risk
  314. ### `wp-accessibility-review`
  315. - Semantic HTML and structure
  316. - Keyboard interaction support
  317. - Focus management
  318. - Form labels and error messaging
  319. - Accessible interactive patterns in themes, blocks, and admin UI
  320. ### `wp-test-strategy`
  321. - Unit vs integration vs E2E test selection
  322. - Risk-based coverage planning
  323. - Existing test discovery and gap analysis
  324. - Regression planning for WordPress features
  325. - Coverage guidance for REST, blocks, admin UI, themes, and WooCommerce
  326. ## Requirements
  327. - [Claude Code](https://claude.ai/code) or Codex
  328. - A local or project-based skill installation
  329. No additional dependencies are required beyond your agent setup.
  330. ## Contributing
  331. Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for setup, structure, and submission guidance.
  332. Common contribution paths:
  333. - Improve or modernize existing guidance
  334. - Add missing edge cases and anti-patterns
  335. - Expand examples and reference docs
  336. - Propose or implement new WordPress skills
  337. ## License
  338. MIT License. See [LICENSE](LICENSE) for details.
  339. ## Changelog
  340. See [CHANGELOG.md](CHANGELOG.md) for release history.
  341. ---
  342. These skills reflect practical WordPress engineering patterns and tradeoffs. They are not affiliated with or endorsed by Claude, Codex, WordPress, WooCommerce, or any hosting platform.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.