juvojustin WP Plugin BP Skill
Operate this WordPress plugin. Keep this file as the router and load command references only when the task calls for them.
Task Routing
| Task | Purpose | Reference |
|---|---|---|
upgrade [scope] |
Sync the plugin with the latest upstream project conventions | references/upgrade.md |
translation [locales] |
Extract, update, translate, and compile plugin translations | references/translation.md |
testing [target] |
Write or debug wp-env PHPUnit application tests | references/testing.md |
qa [scope] |
Run configured quality checks and fix errors | references/qa.md |
action-scheduler [target] |
Add or test Action Scheduler integration | references/action-scheduler.md |
readme [target] |
Update the plugin README from current code and project conventions | references/readme.md |
wp-skills [names] |
Upsert official WordPress agent skills | references/wp-skills.md |
blocks [target] |
Scaffold or maintain Gutenberg blocks | references/blocks.md |
abilities [target] |
Implement or update WordPress Abilities API code | references/abilities.md |
bundling [target] |
Work on wp-scripts entry points, assets, or enqueueing | references/bundling.md |
acf [target] |
Add or maintain ACF integration patterns | references/acf.md |
sentry [target] |
Add or maintain Sentry integration patterns | references/sentry.md |
Routing Rules
- If the request is broad or has no clear task, show the task table grouped by purpose and ask what the user wants to do.
- If the first word matches a task or alias, load that task's reference file and follow it. Everything after the task is the target or arguments.
- If the first word does not match a task, infer the task from the user's intent, load the matching reference file, and proceed.
- If two tasks are equally plausible and the next step would materially differ, ask one concise clarification question.
Do not continue with generic WordPress advice when a task applies. The task reference owns the workflow once selected.
Automatic Task Inference
- Route to
upgradefor: plugin upgrade, sync upstream, migrate to latest project conventions, adopt upstream features, update Loader, update AI commands or skills from upstream. - Route to
translationfor: i18n, translations, translate,.po,.pot,.mo, locale codes likede_DE, text domain,composer run i18n:*. - Route to
testingfor: PHPUnit, application tests,WP_UnitTestCase, factories, test bootstrap, wp-env test container, adding or debugging tests. - Route to
qafor: PHPCS, PHPStan, ESLint, stylelint, linting, static analysis, quality checks, build verification. - Route to
action-schedulerfor: Action Scheduler, async jobs, background jobs, scheduled actions, queues, queue runner. - Route to
readmefor: README, WordPress.org readme, plugin documentation summary, user-facing repository overview. - Route to
wp-skillsfor: WordPress agent skills,wp-block-development,wp-phpstan,wp-rest-api,wp-project-triage,wp-interactivity-api. - Route to
blocksfor: Gutenberg blocks,npm run create-block, block manifests, block editor assets. - Route to
abilitiesfor: WordPress Abilities API, ability categories,add_ability, WP 6.9 abilities. - Route to
bundlingfor:@wordpress/scripts, webpack entry points, build assets, enqueueing, asset localization. - Route to
acffor: Advanced Custom Fields, ACF JSON sync, field groups. - Route to
sentryfor: Sentry SDK, error monitoring, early bootstrap capture.
Skill Scripts
scripts/plugin-replace.php: deterministic identity replacement and setup cleanup helper. Use this script for initialization and upgrade reference rewrites instead of hand-editing placeholders.scripts/upgrade-check.js: automated upgrade comparison. Run withnodeafterplugin-replace.phphas rewritten the cloned reference; it diffs every upgradable area, builds dependency/script mismatch tables, tolerates plugins missing most areas, and prints a report telling you which areas need review and how to fan out subagents. See references/upgrade.md.
Environment
If the host has no working environment (ddev,wp-studio etc) use wp-env.
- Start the development environment:
npm run env:start - Run application tests:
npm run test:php - Run commands:
npm run env:cli -- composer run phpstanornpm run env:cli -- composer run i18n:extract
All PHP and wp-cli commands/tools can run inside wp-env. npm commands need to run on the host.