PHPackages huzaifaalmesbah/wp-boost - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. huzaifaalmesbah/wp-boost ActiveLibrary[Utility & Helpers](/categories/utility) huzaifaalmesbah/wp-boost ======================== Install official WordPress agent skills into your project for Claude Code, Cursor, Copilot, Codex, Windsurf, Zed and more. v0.1.2(1mo ago)114GPL-2.0-or-laterPHPPHP >=8.1CI passing Since Apr 14Pushed yesterdayCompare [ Source](https://github.com/huzaifaalmesbah/wp-boost)[ Packagist](https://packagist.org/packages/huzaifaalmesbah/wp-boost)[ RSS](/packages/huzaifaalmesbah-wp-boost/feed)WikiDiscussions main Synced 1w ago READMEChangelogDependencies (4)Versions (6)Used By (0) wp-boost ======== [](#wp-boost) Install the official **WordPress agent skills** into your project for Claude Code, Cursor, GitHub Copilot, OpenAI Codex, Windsurf, Zed, Gemini CLI, Junie, and OpenCode — the same idea as `laravel/boost`, but for WordPress plugins and block themes. Skills are sourced from [`WordPress/agent-skills`](https://github.com/WordPress/agent-skills). wp-boost bundles a pinned snapshot and can pull the latest on demand. --- Requirements ------------ [](#requirements) - **PHP 8.1+** - **[Composer](https://getcomposer.org) 2.x** ### Don't have Composer yet? [](#dont-have-composer-yet) Check first: ``` composer --version ``` If you see a version like `Composer version 2.x`, you're ready — skip to [Install](#install). If the command isn't found, install it: **macOS / Linux:** ``` curl -sS https://getcomposer.org/installer | php sudo mv composer.phar /usr/local/bin/composer ``` **Windows:** download and run the installer from [getcomposer.org/download](https://getcomposer.org/download). Then make sure Composer's global bin directory is on your `PATH` (you'll install wp-boost there): ``` # find the path composer global config bin-dir --absolute # e.g. /Users/you/.composer/vendor/bin # add to your shell profile (~/.zshrc, ~/.bashrc) export PATH="$HOME/.composer/vendor/bin:$PATH" ``` Reload your shell (`source ~/.zshrc`) and verify: ``` composer --version ``` --- Install ------- [](#install) ``` composer global require huzaifaalmesbah/wp-boost ``` Verify: ``` wp-boost --version ``` --- Use --- [](#use) Inside any WordPress plugin or block theme project: ``` cd /path/to/your-project wp-boost install ``` wp-boost will: 1. **Detect your project type** (plugin, block theme, core) and pre-select recommended skills. 2. **Detect which AI agents you already use** (by looking for `.claude/`, `.cursor/`, `.github/`, etc.) and pre-select them. 3. Let you confirm or change the selection. 4. Copy the right files into each agent's skills directory and write `wp-boost.lock.json`. ### Non-interactive / CI [](#non-interactive--ci) `--yes` accepts detected defaults. Override with flags as needed: ``` wp-boost install --yes # use detected defaults wp-boost install --preset=plugin --yes # force project type wp-boost install --agents=claude_code,cursor --yes # pick agents explicitly wp-boost install --skills=wp-plugin-development --yes # pick skills explicitly wp-boost install --path=/path/to/project --yes # different project path ``` ### Inspect [](#inspect) ``` wp-boost doctor # detected project type, detected agents, available skills ``` ### Get help [](#get-help) Every command has built-in help (provided by Symfony Console): ``` wp-boost # show all commands (same as: wp-boost list) wp-boost --help # top-level help wp-boost --version # print version wp-boost help install # help for a specific command wp-boost help update wp-boost help doctor wp-boost install --help # same thing, -h also works ``` --- Updating -------- [](#updating) There are **two kinds of "update"** and it's important to understand the difference. ### 1. Update wp-boost itself (the CLI tool) [](#1-update-wp-boost-itself-the-cli-tool) Ships new features, bug fixes, and any tweaks to agent definitions (`agents.json`). ``` composer global update huzaifaalmesbah/wp-boost ``` (If you installed per-project instead: `composer update huzaifaalmesbah/wp-boost --dev` inside that project.) ### 2. Update the skills content in your project [](#2-update-the-skills-content-in-your-project) Two sub-cases: **A. Re-sync from the bundled snapshot** — useful after you `composer global update` (the new release may include newer bundled skills), or if you manually edited files and want them reset. ``` cd /path/to/your-project wp-boost update ``` **B. Refresh the global bundle, then apply to the current project** ``` cd /path/to/your-project wp-boost update --remote # shortcut for: wp-boost sync + wp-boost update wp-boost update --remote --upstream # same, but pulls from WordPress/agent-skills@trunk ``` **C. Refresh the global bundle only — no project needed** ``` # works from anywhere, doesn't touch any project wp-boost sync # default: pull from huzaifaalmesbah/wp-boost@main (vetted) wp-boost sync --upstream # opt-in: pull from WordPress/agent-skills@trunk (bleeding edge) ``` Afterwards, run `wp-boost update` inside each project you want to apply the new skills to. This is the fastest way to update many projects: refresh the bundle once, then cheap local syncs everywhere else. ### Two sources to sync from [](#two-sources-to-sync-from) SourceWhen to useTrade-off**`huzaifaalmesbah/wp-boost@main`** (default)Normal useVetted through PR review, ≤7 days behind upstream**`WordPress/agent-skills@trunk`** (`--upstream`)You want the absolute latest or are debugging upstream changesUnvetted — may contain broken/in-progress content### What exactly does `sync` / `--remote` change? [](#what-exactly-does-sync----remote-change) Both refresh **wp-boost's own bundled `skills/` directory** (a copy that lives inside the installed wp-boost package itself, not inside any project). How wp-boost is installedWhat gets modifiedAffects other projects?**Global** (`composer global require`)`~/.composer/vendor/huzaifaalmesbah/wp-boost/skills/`✅ Yes — every project will see the new skills next time you run `wp-boost install` or `wp-boost update` in it**Per-project** (`composer require --dev`)`that-project/vendor/huzaifaalmesbah/wp-boost/skills/`❌ No — only that project's vendored copy`wp-boost update --remote` does the sync **and** re-syncs the current project in one step. Plain `wp-boost sync` just refreshes the bundle. ### "How do I know a project needs `wp-boost update`?" [](#how-do-i-know-a-project-needs-wp-boost-update) wp-boost stamps the bundle's commit SHA into every `wp-boost.lock.json` on install/update. Whenever you run `wp-boost doctor`, it compares the project's stamped SHA against the current bundle's SHA and prints a warning if they differ: ``` Bundle: def5678 from huzaifaalmesbah/wp-boost@main (2026-04-14T08:30:00+00:00) Project: abc1234 (installed 2026-04-10T14:02:00+00:00) ⚠ Project is using skills from bundle abc1234; current bundle is def5678. Run `wp-boost update` to apply the new skills. ``` After `wp-boost update`, the SHAs match and the warning goes away. ### Typical workflows [](#typical-workflows) **Global-install users (most common):** ``` # refresh the global bundle once, from anywhere wp-boost sync # then apply to each project you care about cd ~/project-a && wp-boost update # fast local sync, no network cd ~/project-b && wp-boost update ``` **Per-project install:** run `wp-boost update --remote` inside each project you want to refresh. --- Commands -------- [](#commands) CommandPurpose`wp-boost install`Interactive install with auto-detection. Flags: `--agents=`, `--skills=`, `--preset=`, `--yes`, `--path=``wp-boost update`Re-sync installed skills from the bundled snapshot.`wp-boost update --remote`Refresh the bundle (see `sync` below), then re-sync the current project.`wp-boost sync`Refresh the global bundle from `huzaifaalmesbah/wp-boost@main`. No project needed — run from anywhere.`wp-boost sync --upstream`Refresh the global bundle from `WordPress/agent-skills@trunk` (bleeding edge, bypasses vetted channel).`wp-boost doctor`Print detected project type, detected agents, and available skills.--- Supported agents ---------------- [](#supported-agents) Driven by [`agents.json`](./agents.json): AgentSkills directoryClaude Code`.claude/skills/`Cursor`.cursor/rules/` (`.mdc` format)GitHub Copilot`.github/instructions/`OpenAI Codex CLI`.codex/skills/`Windsurf`.windsurf/rules/`Zed`.zed/skills/`Gemini CLI`.gemini/skills/`JetBrains Junie`.junie/skills/`OpenCode`.opencode/skills/`--- What gets written to your project --------------------------------- [](#what-gets-written-to-your-project) After `wp-boost install` (depending on agents selected): ``` your-project/ ├── .claude/skills//SKILL.md ├── .cursor/rules/.mdc ├── .github/instructions/.md ├── ... └── wp-boost.lock.json # records installed agents + skills ``` Re-running `wp-boost install` or `wp-boost update` overwrites existing skill files with the latest content — safe to do anytime. --- Uninstall --------- [](#uninstall) ``` composer global remove huzaifaalmesbah/wp-boost ``` Installed skill files stay in your project. Delete `.claude/skills/`, `.cursor/rules/`, etc. manually and remove `wp-boost.lock.json` if you no longer want them. --- Contributing & reporting issues ----------------------------------- [](#contributing--reporting-issues) Where you file things depends on what you're reporting — the CLI tool lives here, the skill content lives upstream at [`WordPress/agent-skills`](https://github.com/WordPress/agent-skills). If you want to…File it atReport a skill-content bug (wrong info inside a `SKILL.md`)[WordPress/agent-skills · issues](https://github.com/WordPress/agent-skills/issues) · [PRs](https://github.com/WordPress/agent-skills/pulls)Propose a new skill[WordPress/agent-skills · issues](https://github.com/WordPress/agent-skills/issues) · [PRs](https://github.com/WordPress/agent-skills/pulls)Report a wp-boost CLI bug (install/update/sync/doctor)[huzaifaalmesbah/wp-boost · issues](https://github.com/huzaifaalmesbah/wp-boost/issues) · [PRs](https://github.com/huzaifaalmesbah/wp-boost/pulls)Add support for a new AI agent[huzaifaalmesbah/wp-boost · issues](https://github.com/huzaifaalmesbah/wp-boost/issues) · [PRs](https://github.com/huzaifaalmesbah/wp-boost/pulls)Improve detection, prompts, docs, CI[huzaifaalmesbah/wp-boost · issues](https://github.com/huzaifaalmesbah/wp-boost/issues) · [PRs](https://github.com/huzaifaalmesbah/wp-boost/pulls)See [CONTRIBUTING.md](./CONTRIBUTING.md) for the full dev guide: local setup, project structure, adding a new AI agent, testing, and release process. --- Credits & attribution ------------------------- [](#credits--attribution) wp-boost is a downstream **distributor**, not an author of the skill content. Everything inside the `skills/` directory is an unmodified redistribution from upstream — please credit upstream first whenever you share or fork this project. ### Primary credit — skill authors [](#primary-credit--skill-authors) > **[WordPress/agent-skills](https://github.com/WordPress/agent-skills)** — the WordPress contributors who author, review, and maintain every `SKILL.md` this tool installs. All skill content, examples, and guidance are their work and their copyright, licensed GPL-2.0-or-later. If a skill helped you, please **★ star their repo** and file issues / PRs against **their** tracker, not this one. Skill-content changes made against wp-boost cannot be accepted — they must land upstream so the whole WordPress + AI community benefits. ### Snapshot provenance [](#snapshot-provenance) The bundled `skills/` directory is a pinned snapshot of `WordPress/agent-skills@trunk`. The exact upstream commit is recorded in [`skills/.bundle.json`](./skills/.bundle.json) (`sha`, `syncedAt`, `source`) and stamped into every project's `wp-boost.lock.json` on install, so you can always trace a skill file back to the upstream commit it came from. An automated job — [`.github/workflows/sync-skills.yml`](./.github/workflows/sync-skills.yml) — runs every Monday and opens a PR bumping the snapshot whenever upstream has moved. Under normal conditions the bundle is **never more than 7 days behind** `WordPress/agent-skills@trunk`. ### Also thanks to [](#also-thanks-to) - **The WordPress community** — for building and maintaining the ecosystem this tool serves. - **[`laravel/boost`](https://github.com/laravel/boost)** — the inspiration for the UX pattern: auto-detect the project + the agents the developer already uses, then install the right skills in one shot. wp-boost does the same job for the WordPress ecosystem. - **Every contributor** to the AI coding agents this tool targets (Claude Code, Cursor, GitHub Copilot, Codex, Windsurf, Zed, Gemini CLI, Junie, OpenCode) for shipping the skills / rules / instructions protocols this installer plugs into. --- License ------- [](#license) wp-boost is licensed under the **GNU General Public License v2.0 or later** (GPL-2.0-or-later), matching [`WordPress/agent-skills`](https://github.com/WordPress/agent-skills) and the wider WordPress ecosystem. See [LICENSE](./LICENSE) for the full text. The bundled content in `skills/` is an unmodified redistribution from `WordPress/agent-skills` and remains under its original GPL-2.0-or-later license, copyright the WordPress contributors. ### Health Score 39 — LowBetter than 84% of packages Maintenance95 Actively maintained with recent releases Popularity10 Limited adoption so far Community8 Small or concentrated contributor base Maturity36 Early-stage or recently created project Bus Factor1 Top contributor holds 52.9% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~3 days Total 3 Last Release 51d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/d03c2e9e1d7376b3496c3946077219c3dfe3820457ce80f381029e9053bed770?d=identicon)[huzaifaalmesbah](/maintainers/huzaifaalmesbah) --- Top Contributors [![huzaifaalmesbah](https://avatars.githubusercontent.com/u/63150399?v=4)](https://github.com/huzaifaalmesbah "huzaifaalmesbah (9 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (8 commits)") --- Tags wordpressaicursorcopilotclaudeagent-skills ### Embed Badge ![Health badge](/badges/huzaifaalmesbah-wp-boost/health.svg) ``` [![Health](https://phpackages.com/badges/huzaifaalmesbah-wp-boost/health.svg)](https://phpackages.com/packages/huzaifaalmesbah-wp-boost) ``` ### Alternatives [matomo/matomo Matomo is the leading Free/Libre open analytics platform 21.6k38.2k](/packages/matomo-matomo)[cognesy/instructor-php The complete AI toolkit for PHP: unified LLM API, structured outputs, agents, and coding agent control 317117.1k1](/packages/cognesy-instructor-php)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 101466.4k44](/packages/friendsoftypo3-content-blocks)[illuminate/console The Illuminate Console package. 13045.3M6.1k](/packages/illuminate-console)[shopware/core Shopware platform is the core for all Shopware ecommerce products. 585.4M506](/packages/shopware-core)[whatsdiff/whatsdiff See what's changed in your project's dependencies 761.1k](/packages/whatsdiff-whatsdiff) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)