Download the PHP package trk/processwire-boost without Composer

ProcessWire Boost

AI context bridge for ProcessWire CMS/CMF.

Boost ensures AI coding agents produce expert-level ProcessWire code by providing structured context: guidelines that encode best practices, task playbooks (skills) that teach specific patterns, a schema map for project awareness, and a JSON-RPC (MCP) server for live system access.

This is not a CLI tool collection — Boost is a knowledge layer. It sits between your ProcessWire project and the AI agent, ensuring every code suggestion, module scaffold, and schema change follows established conventions.

Table of Contents

• Why Boost?
• How It Works
• Requirements
• Installation
• Quick Start
• Context Layers
  • Guidelines
  • Skills (Task Playbooks)
  • Schema Map
  • MCP Server (Live Access)
• Agent System
• Module Integration
• Commands
• Configuration
• Troubleshooting
• License

Why Boost?

AI agents can write PHP — but writing correct ProcessWire code requires deep context:

Boost turns a general-purpose AI into a ProcessWire specialist.

How It Works

Architecture

Four context layers, each serving a different purpose:

Runtime Flow

Here is a brief outline of how an AI works under the hood at runtime with these layers:

1. User asks for a task (e.g., "Create a migration to add a blog template").
2. Agent reads Guidelines (e.g., AGENTS.md) for base framework rules & conventions.
3. Agent activates relevant Skill (like pw-migrations) providing the specific, step-by-step workflow required.
4. Agent reads Schema Map (map.json) to learn the existing project templates, roles, and fields.
5. Agent queries MCP Server (pw_schema_read etc.) for live configurations or logs natively inside the processwire environment.
6. Agent generates the code, reliably completing the task with full system awareness.

Requirements

Installation

Note: processwire-console provides the vendor/bin/wire CLI runner. Boost commands are auto-discovered via Composer extra metadata — no manual registration needed.

Quick Start

1. Run the Installer

2. What Gets Generated

3. Verify

Context Layers

Guidelines

Guidelines are the always-on context layer — they are compiled into a single instruction block and embedded in the agent's primary instruction file (e.g., AGENTS.md, CLAUDE.md).

Every time the agent processes a prompt, it reads these rules. This is where conventions, security patterns, and API usage rules live.

What Gets Compiled

Source Priority

1. Core — resources/boost/guidelines/*.md (7 files)
2. Module — {module}/.agents/guidelines/*.md (third-party modules)
3. Fallback — {module}/AGENTS.md (if no guidelines directory exists)

Merge Strategy

This means your custom instructions in CLAUDE.md or AGENTS.md survive across reinstalls.

Skills (Task Playbooks)

Skills are on-demand context — the agent activates a specific skill when the current task matches its domain. Each skill is a SKILL.md file containing a complete workflow guide.

Unlike guidelines (which are always present), skills are loaded only when relevant. This keeps the context window efficient while providing deep expertise when needed.

Built-in Skills (23)

Module-Provided Skills

Third-party ProcessWire modules can ship their own Boost skills. When selected during boost:install, these are merged alongside the built-in skills:

How Skills Guide Agents

When an agent encounters a task like "create a migration to add a blog template", the pw-migrations skill activates and provides:

• Correct creation order: Field → Fieldgroup → Template → Page
• Safe rollback order: Page → Template → Fieldgroup → Field
• Pre-flight safety checks (e.g., "don't delete a field that's still attached to templates")
• Working stub selection (--type=create-template)

Without this skill, the agent would guess at the API and likely produce unsafe or incorrect migration code.

Skill Sync Model

ProcessWire Boost 0.1.x keeps skills canonical in .agents/skills/{skillName}/SKILL.md.

• Agent-specific skill copies are not generated during install/update.
• exportSkill() overrides remain available for future agent-specific export flows.
• This keeps updates deterministic and avoids redundant skill trees across IDE folders.

Schema Map

The schema map (map.json) gives agents project-specific awareness without requiring a live database connection.

Generated on every boost:install run, it contains:

This map enables agents to:

• Generate code that references real template and field names instead of placeholders
• Avoid creating duplicate fields or templates
• Understand the permission structure before creating access control logic

Field Schema Extenders (Optional)

Boost supports optional field schema extenders so non-core or complex fieldtypes can append additional metadata.

• Generic metadata is appended under fields.{name}.extra.
• The extension key fields is reserved and promoted to top-level fields.{name}.fields for nested field definitions.
• Built-in repeater extender support covers FieldtypeRepeater and FieldtypeFieldsetPage, adding nested field schema entries (id, type, label) keyed by subfield name.

Discovery paths:

• site/boost/schema/field-extenders.php
• site/modules/*/.agents/schema/field-extenders.php
• wire/modules/*/.agents/schema/field-extenders.php

Each manifest should return an array of extender class names (or instances) implementing Totoglu\Console\Boost\Schema\FieldSchemaExtender. Extenders run in discovery order; if multiple extenders return the same key, the later value wins.

Extender failures are non-fatal: Boost keeps generating the base schema and logs errors to processwire-boost.

MCP Server (Live Access)

The MCP server provides real-time access to the running ProcessWire system via JSON-RPC over stdio.

This is the most powerful context layer — it enables agents to inspect live data, run selectors against real pages, read logs, and manage modules without leaving the conversation.

Available Tools (28)

MCP Config Formats

Boost auto-generates MCP configuration in each agent's native format during boost:install:

JSON — Standard Context (Claude Code, Cursor, Copilot, Amp, Junie, Kiro):

JSON — ${workspaceFolder} (Trae):

TOML (Codex):

OpenCode (nested command array):

Agent System

Boost uses a polymorphic Agent class hierarchy. Each agent declares how it wants to receive context:

Supported Agents

Auto Path Resolution: Each agent declares its mcpPathStrategy() via the McpPathStrategy enum. No manual configuration needed — paths are resolved automatically.

Detection & Filtering: The installer auto-detects existing agent footprints and only offers agents compatible with the selected feature set.

Adding a Custom Agent

Module Integration

Third-party ProcessWire modules can expose their own guidelines and skills to Boost.

Directory Structure

Discovery

1. Boost scans site/modules/ and wire/modules/ for .agents/ directories
2. Guidelines from .agents/guidelines/*.md are compiled into the agent instruction file
3. Skills from .agents/skills/*/SKILL.md are synchronized into the central Boost skill store
4. Fallback: if no .agents/guidelines/ exists, AGENTS.md in the module root is used

Tip: After installing a new module that provides Boost skills, run php vendor/bin/wire boost:update to sync the new guidelines and skills into your workspace.

Site-Level Overrides

CLI Commands

boost:install

Manage AI helper setup (ProcessWire Boost). Select features to install/update, deselect to remove.

Usage:

Examples:

boost:update

Re-sync ProcessWire Boost guidelines & skills from saved configuration.

• Can discover newly available Boost-aware modules and persist them into .agents/boost.json
• Can skip central skill sync when only guidelines or MCP config need refreshing

Usage:

Examples:

boost:mcp

Start the ProcessWire MCP server (JSON-RPC over stdio).

Usage:

Examples:

boost:build:docs

Generate ProcessWire Core API reference documentation from source files.

Usage:

Examples:

boost:add-skill

Add skills from a remote GitHub repository.

• Remote repositories must expose skills as SKILL.md.
• A local heuristic audit runs before installation unless --skip-audit is passed.
• Successful installs trigger boost:update automatically unless --skip-update is passed.

Usage:

Examples:

Configuration

boost.json

The installer stores its state in .agents/boost.json:

This file enables incremental updates — rerunning boost:install preserves your selections as defaults.

Troubleshooting

Skills Not Appearing

MCP Server Not Working

Guidelines Not Updating

The merge strategy preserves custom content. To force regeneration:

ProcessWire Core Not Found

Language Policy

All code, documentation, comments, and variable names must be written in English.

Contributing

1. Open an issue describing the change
2. Follow existing code style (strict types, PHPDoc, camelCase)
3. Ensure all PHP files pass php -l linting
4. Test with at least two different agents

License

MIT