wp-dev.ucsc

This skill should be used when the user asks to "run the WordPress app", "start wp-dev.ucsc", "launch and drive the plugin", "open the editor", "interact with the block", or "demonstrate this change" in the UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks) Docker environment. Use verify for a specific acceptance criterion and validate for PHP, Jest, or e2e tests.

This skill should be used when the user asks to "add new behavior", "create a new block", "add a feature", "implement editor controls", "add frontend output", or describes new functionality for UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks) that is not a defect fix.

This skill should be used when the user asks to "fix a block", "debug an issue", "something is broken", "block not showing", "wrong output", or reports any defect in a block, GUI, or app under UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks). Require the target and a plain-language problem description before investigating.

This skill should be used when the user asks to "add a block", "create a Gutenberg block", "implement a feature", "modify block code", "extend a block", or when feature/fix scope is already defined and implementation is ready to begin on UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks).

This skill should be used when the user asks to "submit feedback", "send feedback", "give feedback about a skill", "report a bug in the plugin", "report a problem with run/validate/verify", "file a suggestion for ucsc-wp-block-dev", or invokes `:feedback` (plugin-related only; not for the WordPress feedback block).

This skill should be used when the user asks to "list skills", "what can you do", "show available commands", "what WordPress block skills are available", or invokes `:hub` (lists plugin inventory and handles session block target resolution).

This skill should be used when the user asks to "maintain the plugin", "validate the plugin structure", "run the plugin self-tests", "review or promote a skill", "check ADR consistency", "study upstream plugin patterns", "publish the maintainer docs", or prepare ucsc-wp-block-dev for release.

This skill should be used when the user asks to "create a PHP test", "run the PHP tests", "create a Jest test", "run the Jest tests", "create an e2e test", "run the e2e tests", or validate a UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks) feature, fix, or Jira acceptance criterion with an automated test suite. Use verify instead for live editor or frontend behavior.

This skill should be used when the user asks to "verify this change", "confirm this works", "prove this acceptance criterion", "check the rendered block", or demonstrate that a UCSC block plugins (ucsc-blocks, ucsc-gutenberg-blocks) change behaves correctly in the running WordPress editor or frontend without substituting automated tests or type checks.

This skill should be used when the user asks to "capture lessons learned", "update the skills from this session", "record this gotcha", "preserve this pattern", or persist reusable domain knowledge at the end of a fix, feature, review, or run session. Use it to enrich ucsc-wp-block-dev skill references, not to produce a task summary.

This skill should be used when the user asks to "review this diff", "review this branch", "check this PR", "review this file", "check this change for accessibility", "look for security issues", or review a Jira-scoped WordPress block change for bugs, regressions, and missing tests.