superpowers-sage:block-refactoring

To fix design system drift in ACF Composer blocks, you analyze block rendering against a reference to report divergences, classify v1, v2, or mixed structures, and produce an approval-gated report with safe changes.

Cleaning up unused CSS in WordPress custom blocks involves analyzing block rendering and CSS usage to identify unused custom properties and selectors, then proposing safe removals through an approval-gated report.

Expanding $styles variations with newly available tokens requires analyzing the block structure, detecting incomplete variations, and proposing upgrades aligned with the latest design conventions.

You can migrate legacy v1 ACF Composer blocks to v2 without rebuilding by classifying the v1, v2, or mixed structure, detecting migration gaps, and generating safe Phase 7 changes.

To start an ACF Composer block refactoring task, you need to provide the block identity via the block class name or block slug so the tool can resolve it and optionally verify against a reference.

You should avoid refactoring existing ACF Composer blocks when you lack a provided class name or slug to resolve block identity, as the process requires resolving identity before generating safe changes.