Review a block extension for best practices.
Ask the user which extension to review, then check that the extension:
- •
Works WITH WordPress attributes
- •Uses
layout.typewhen extending Group block - •Doesn't create duplicate layout systems
- •Respects WordPress native attributes
- •Uses
- •
Shows controls conditionally
- •Grid controls only shown when
layout.type === 'grid' - •Flex controls only shown when layout is flex
- •Controls make sense in current context
- •Grid controls only shown when
- •
Doesn't duplicate WordPress toolbar
- •No layout selectors that conflict with toolbar icons
- •No controls that replicate native WordPress features
- •Enhances rather than replaces
- •
Uses proper filter hooks
- •
blocks.registerBlockTypefor attributes - •
editor.BlockEditfor inspector controls - •
blocks.getSaveContent.extraPropsfor save classes - •Proper filter names with namespace
- •
- •
Includes responsive considerations
- •Desktop/tablet/mobile variants
- •Mobile-first approach
- •Proper breakpoints
- •
Follows project patterns
- •Matches patterns in
.claude/claude.md - •Uses consistent naming (dsg prefix)
- •Proper file structure
- •No versioned filenames (no -v2, -v3, etc.)
- •Matches patterns in
- •
CSS Strategy
- •Uses
!importantwhen overriding WordPress defaults - •Targets correct elements (.wp-block-group__inner-container for Group)
- •Includes both frontend and editor styles
- •Uses
Provide a detailed review with specific code examples of any issues found and recommendations for fixes.