orbit-block-patternslisted

# 🪐 orbit-block-patterns — Block patterns audit Patterns are the easiest content win for plugin teams — pre-built layouts users insert and adapt. Most plugins ship them wrong. --- ## Quick start ```bash claude "/orbit-block-patterns Audit ~/plugins/my-plugin's block patterns." ``` --- ## What it checks ### 1. Patterns registered with `register_block_pattern()` ```php register_block_pattern( 'my-plugin/hero', [ 'title' => __( 'Hero', 'my-plugin' ), 'description' => __( 'Big hero with CTA', 'my-plugin' ), 'categories' => [ 'my-plugin' ], 'keywords' => [ 'hero', 'banner' ], 'content' => '<!-- wp:cover --><!-- /wp:cover -->', 'viewportWidth' => 1280, ] ); ``` ### 2. Custom category registered ```php register_block_pattern_category( 'my-plugin', [ 'label' => __( 'My Plugin', 'my-plugin' ), ] ); ``` ### 3. Pattern content uses correct block names **Whitepaper intent:** Patterns reference block names. If your plugin's block is `my-plugin/example`, the pattern's content must use exactly that — typos fail silently and the pattern shows blank. ### 4. `viewportWidth` set Without it, patterns get cropped in the inserter preview. Set `viewportWidth: 1280` (or 1440 for desktop-only). ### 5. Synced patterns (WP 6.3+) Synced patterns share data across all uses. Useful for footers / headers / CTAs. ```php register_block_pattern( 'my-plugin/synced-cta', [ 'content' => '...', 'inserter' => true, // synced via Pattern Directory or wp_block CPT ] );