Block-specific patterns appear automatically when certain blocks are added, like query loop patterns that appear when inserting query loop blocks. These patterns target specific block types through the blockTypes registration argument.
Header template part replacement options are another example – patterns registered specifically for header template part blocks that appear in the replacement interface.
This targeting system reduces interface clutter by showing relevant patterns only when appropriate. Users see patterns that make sense for their current context rather than all available patterns.
Block-specific registration makes patterns more discoverable and contextually relevant, improving the editing experience by surfacing appropriate design options at the right moment.