What problem does it solve? Designing block content structures for AEM Edge Delivery Services is error-prone: models with too many columns, spreadsheet-like header rows, or misused configuration patterns make authoring painful in Google Docs, SharePoint, and the Universal Editor. This Skill provides a structured four-step workflow to design semantic, predictable, and reusable content models before any TypeScript block code is written. ## Core Features & Use Cases - Four canonical model patterns: Guides selection among Standalone, Collection, Configuration, and Auto-Blocked models with good and bad examples drawn from real project blocks (hero, cards, activities). - Validation checklist: Enforces best practices such as the 4-cells-per-row maximum, semantic formatting over config cells, and block variants instead of style key-value pairs. - Advanced scenario guidance: Covers nested blocks, item-level configuration in collections, list handling, and form modeling strategies. - Use Case: When creating a new cards block, invoke this Skill during Step 3 of content-driven development to produce a documented table structure that authors can use across Google Docs, SharePoint, and the Universal Editor. ## Quick Start Ask the AI to design a content model for a new AEM Edge Delivery block, describing the block's purpose and required content elements.
