What problem does it solve? WordPress block patterns and templates often fail silently — no errors, no exceptions — when layout types, spacing attributes, or pattern references behave differently than expected, costing hours of debugging. This Skill provides a checklist of verified core behaviors so you can avoid or quickly diagnose these pitfalls before writing or debugging pattern markup. ## Core Features & Use Cases - Layout Pitfall Reference: Documents the real accepted values for layout.type, the cross-fill behavior of contentSize/wideSize, and why margin and blockGap are unreliable inside default/constrained layouts. - Pattern Context Diagnosis: Explains why wp:pattern references lose ambient block context inside query loops and how to fix it with PHP require or expanded markup in .html templates. - Serialization and Validation Traps: Covers __experimentalSkipSerialization attributes, bare HTML tags breaking block validation, DB-stored overrides shadowing file edits, caching layers masking changes, and php -l missing dangling require() calls. - Use Case: A pattern renders empty on the front end but passes a CLI do_blocks() test — consult this Skill to identify the context-loss pitfall and inline the referenced pattern correctly. ## Quick Start Review this checklist before writing or debugging any WordPress block pattern, template, or template part to catch silent-failure pitfalls early.
