processwire-boost

Use when building, structuring, or refactoring native backend modules for ProcessWire using PHP 8.4 and strict typing.

Use when designing, structuring, or rendering HTML for ProcessWire Admin interfaces, custom Process modules, or Inputfields.

Use when brainstorming or designing ProcessWire modules, templates, field schemas, or hooks to resolve ambiguity and validate architecture before implementation.

Use when creating, executing, or managing Pest tests within ProcessWire or ProcessWire modules, including Test-Driven Development (TDD) tasks.

Use when encountering any bug, test failure, blank screen of death, or unexpected behavior in ProcessWire before proposing fixes.

Use when creating or updating module documentation, package READMEs, architecture guides, or CLI command references for ProcessWire projects.

Use when creating implementation plans from approved specifications to ensure ProcessWire-native architecture, safe migration structures, and strict test-driven task execution.

Use when creating or improving Boost skills for ProcessWire agents to ensure optimal CSO formatting and testing requirements.

Use when working with Laravel Prompts/Symfony Console command patterns, or when determining the correct, context-safe way to access ProcessWire API variables like $page, $pages, or $user.

Use when extending ProcessWire's base Page class to create specialized, strongly-typed custom classes representing specific templates.

Use when building custom database fieldtypes and their corresponding interface inputfields in ProcessWire.

Use when deploying discrete file validation architectures inside ProcessWire assessing security and normalization workflows via FileValidator.

Use when creating independent frontend rendering systems explicitly extending the ProcessWire Markup module ecosystem.

Use when constructing custom admin page pipelines, dashboards, or routing structures within ProcessWire implementing isolated Process models and RBAC.

Use when building Textformatter modules to securely and dynamically format string-based fields immediately prior to output rendering in ProcessWire.

Use when auditing ProcessWire modules, hooks, templates, or MCP endpoints for security vulnerabilities like OWASP, input sanitization, RBAC, CSRF, and SQL injections.

Use when utilizing ProcessWire URL/Path hooks to create custom routing, virtual pages, or API endpoints without physical backend templates.

Use when toggling the application's maintenance mode (down/up) in ProcessWire and managing downtime configuration.

Use when creating, dispatching, or interacting with Queue jobs in ProcessWire (processwire-console file-based queues).

Use when creating, scheduling, or managing time-based tasks in ProcessWire via the CronExpression wrapper.

Use when creating, dispatching, or interacting with Database Seeding in ProcessWire (processwire-console file-based seeders).

Use when constructing ProcessWire Selectors or manipulating Page objects — finding, filtering, creating, editing, trashing, and deleting pages.

Use when creating, running, rolling back, or managing ProcessWire schema migrations via the CLI.