Download the PHP package huzaifaalmesbah/wp-boost without Composer

On this page you can find all versions of the php package huzaifaalmesbah/wp-boost. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of huzaifaalmesbah/wp-boost

Informations about the package 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. wp-boost bundles a pinned snapshot and can pull the latest on demand.

Requirements

Don't have Composer yet?

Check first:

If you see a version like Composer version 2.x, you're ready — skip to Install.

If the command isn't found, install it:

macOS / Linux:

Windows: download and run the installer from getcomposer.org/download.

Then make sure Composer's global bin directory is on your PATH (you'll install wp-boost there):

Reload your shell (source ~/.zshrc) and verify:

Install

Verify:

Use

Inside any WordPress plugin or block theme project:

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

--yes accepts detected defaults. Override with flags as needed:

Inspect

Get help

Every command has built-in help (provided by Symfony Console):

Updating

There are two kinds of "update" and it's important to understand the difference.

1. Update wp-boost itself (the CLI tool)

Ships new features, bug fixes, and any tweaks to agent definitions (agents.json).

(If you installed per-project instead: composer update huzaifaalmesbah/wp-boost --dev inside that 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.

B. Refresh the global bundle, then apply to the current project

C. Refresh the global bundle only — no project needed

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

Source When to use Trade-off
huzaifaalmesbah/wp-boost@main (default) Normal use Vetted through PR review, ≤7 days behind upstream
WordPress/agent-skills@trunk (--upstream) You want the absolute latest or are debugging upstream changes Unvetted — may contain broken/in-progress content

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 installed What gets modified Affects 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?"

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:

After wp-boost update, the SHAs match and the warning goes away.

Typical workflows

Global-install users (most common):

Per-project install: run wp-boost update --remote inside each project you want to refresh.

Commands

Command Purpose
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

Driven by agents.json:

Agent Skills directory
Claude 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

After wp-boost install (depending on agents selected):

Re-running wp-boost install or wp-boost update overwrites existing skill files with the latest content — safe to do anytime.

Uninstall

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

Where you file things depends on what you're reporting — the CLI tool lives here, the skill content lives upstream at WordPress/agent-skills.

If you want to… File it at
Report a skill-content bug (wrong info inside a SKILL.md) WordPress/agent-skills · issues · PRs
Propose a new skill WordPress/agent-skills · issues · PRs
Report a wp-boost CLI bug (install/update/sync/doctor) huzaifaalmesbah/wp-boost · issues · PRs
Add support for a new AI agent huzaifaalmesbah/wp-boost · issues · PRs
Improve detection, prompts, docs, CI huzaifaalmesbah/wp-boost · issues · PRs

See CONTRIBUTING.md for the full dev guide: local setup, project structure, adding a new AI agent, testing, and release process.

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

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

The bundled skills/ directory is a pinned snapshot of WordPress/agent-skills@trunk. The exact upstream commit is recorded in 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 — 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

License

wp-boost is licensed under the GNU General Public License v2.0 or later (GPL-2.0-or-later), matching WordPress/agent-skills and the wider WordPress ecosystem. See 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.

All versions of wp-boost with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
symfony/console Version ^6.4 || ^7.0
symfony/process Version ^6.4 || ^7.0
symfony/filesystem Version ^6.4 || ^7.0
laravel/prompts Version ^0.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package huzaifaalmesbah/wp-boost contains the following files

Loading the files please wait ...