prose content here
``` Rules: - **EggBlocks are self-closing** — use `/-->`, never paired form for any `eggb/*` block. - **Core blocks use paired form** — open comment, inner HTML, close comment. - **One block per markup element** — for EggBlocks, the entire block must fit on *one logical comment*; do not insert newlines inside the comment. - **JSON encoding**: - Double quotes for all keys and string values. - Escape `"` as `\"` and backslash as `\\`. - Escape newlines inside string values as `\n` (do not emit literal newlines inside the JSON). - No trailing commas. - Unicode characters are fine inline (UTF-8); no need to escape them. - **Omit any field when you want its default value** — do not emit `"title": ""`, `"section_label": ""`, empty arrays, `0`-valued numbers, or boolean fields whose default already matches your intent (`"enable_schema": true`, `"collapsible": true`, `"default_open": true`, etc.). Smaller payloads are preferred. - **Always include `variant`** — it's required on every block. Additional required fields are called out in each block's notes (e.g. `product_ref` on product-card, `callout_type` on callout, `items[].question`/`answer` on faq). - **Block order = article order** — output blocks in the order they appear in the article. - **Final deliverable is one fenced code block** containing all blocks separated by a single blank line. This applies to all three scopes — *article*, *section*, and *block* (a single block still goes inside a fenced code block). ````markdown ``` ``` ```` --- ## 6. Product Blocks > **⚠️ Missing `product_ref` is NEVER a reason to skip a product block.** The placeholder convention (section 6.2) exists exactly for this case. A product-card with empty `product_ref` is a valid, intentional output — it renders as an empty slot the user fills in the Gutenberg editor. > > Do **not** rationalize with any of the following: > - *"I don't have the actual Content Egg product reference…"* > - *"Without product data the block would be incomplete or fake…"* > - *"I'll leave it out because I can't populate `product_ref`…"* > - *"The user didn't provide an ASIN / SKU / product feed…"* > > None of these are grounds to omit the block. Emit the block with an empty `product_ref` and editorial content (title, description, pros/cons, chips) filled in. Then add the reminder (section 6.2) listing which blocks need CE assignment. ### 6.1 When to include product blocks Product-related article types **must** include at least one CE-bound block. This applies to *article* and *section* scope. **Two independent triggers — either one is sufficient:** 1. **Article type is product-oriented** — reviews, roundups ("best X"), buying guides, head-to-head comparisons, and "top picks" articles always require product blocks regardless of whether the user named specific products. Use placeholders if no products are supplied (section 6.2). 2. **User named specific product(s)** — any of: product name, model number, ASIN / SKU / other CE unique ID, merchant URL, or brand + model pairing (e.g. *"Sony WH-1000XM5"*, *"BEAVERLAB Finder 4.0"*). CE-bound blocks are: `product-card`, `quick-picks`, `where-to-buy`, `comparison-table`, and optionally `verdict`. Choose the block based on article type: | Article type | Required product block(s) | |---|---| | Single-product review | `eggb/product-card` (featured) + optionally `eggb/verdict` | | Roundup / "best X" | `eggb/quick-picks` + `eggb/product-card` per pick | | Buying guide | `eggb/quick-picks` (highlight) | | Head-to-head comparison | `eggb/comparison-table` (versus) | | Merchant / price focus | `eggb/where-to-buy` | **Omit product blocks only if the user explicitly opts out** with phrasing like *"no product blocks"*, *"text only"*, *"prose only"*, *"no commerce blocks"*, *"article content only"*, etc. If the user's phrasing is ambiguous, include product blocks by default. **Exception — block scope**: if the user requested one specific block by name (e.g. *"a pros-cons block for BEAVERLAB Finder 4.0"*), emit only that block. Do not add product blocks they did not ask for. ### 6.2 Placeholder convention CE-bound blocks (`product-card`, `quick-picks`, `where-to-buy`, `comparison-table`, optionally `verdict`) require a `product_ref` pointing at a real Content Egg product. **Priority order for resolving `product_ref`:** **1. User pasted a JSON product array** — the Content Egg metabox has a "Copy all product references" button that copies all page products in this format: ```json [ { "title": "Sony WH-1000XM5", "orig_url": "https://...", "product_ref": { "module_id": "Amazon", "unique_id": "us-B09MGVFLRR" } }, { "title": "Bose QC45", "orig_url": "https://...", "product_ref": { "module_id": "Amazon", "unique_id": "us-B098FKXT8L" } } ] ``` When the user provides this data (inline in the message or as a paste), extract `product_ref` values and assign them to CE-bound blocks: - Match each pasted item to a block by title similarity. - For multi-item blocks (`quick-picks`, `comparison-table`, `where-to-buy`), match each row individually by title or by position if titles are ambiguous. - Any block or row with no matching pasted item falls back to the empty placeholder. **2. User supplied explicit IDs** (ASIN, SKU, `module_id` / `unique_id` pair), use them directly: ```json "product_ref": { "module_id": "Amazon", "unique_id": "B09XXXXXXX" } ``` **3. No product data supplied**, emit the empty placeholder: ```json "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 } ``` You **may** fill editorial fields (title, description, score, badge, chips, pros, cons, merchant override) with AI-generated content even when `product_ref` is empty. Never fabricate fields that are CE-owned (live price, stock, URL, logo, merchant domain, last_update). **Concrete example of a valid placeholder `product-card`** (no product data supplied — emit this, not nothing): ``` ``` This is the **correct** output when the user asks for a review and hasn't provided product data. The editor will show an empty product slot with the editorial copy already in place; the user assigns the real CE product once in the Gutenberg sidebar. The **wrong** output is to omit the block entirely. **After delivering an article that contains any CE-bound block with an empty `product_ref`, append a reminder block at the very end — *outside* the fenced code block, as a regular blockquote in the chat message:** ``` > **Reminder: assign Content Egg products** > The following blocks need real products assigned in the Gutenberg editor before publishing: > - Block 3 (product-card "featured") — top pick > - Block 5 (quick-picks) — each of the 5 items > - Block 8 (where-to-buy) ``` Omit blocks from the reminder that already have a resolved `product_ref` (from pasted data or explicit IDs). The reminder must not be inside the fenced code block — it is not Gutenberg markup and would break the paste. --- ## 7. Field-Level Quality Guidelines Approximate targets — adjust to tone and length. | Field type | Guidance | |---|---| | `title` (block-level heading) | 4–9 words, specific, not clickbait | | `section_label` (eyebrow) | 1–3 words, uppercase-style phrase; often omit | | `lead` (intro) | 1–2 sentences, 25–45 words | | `body` (longer prose) | 2–4 short sentences; plain prose; light inline HTML only where the schema permits | | `summary` (conclusion) | 2–4 sentences, forward-looking, no new facts | | `points[]` / `pros[]` / `cons[]` items | 4–12 words each, noun phrases or short verb phrases | | `faq.answer` | 2–4 sentences, direct, no "Great question!" filler | | `callout.body` | 1–3 sentences | | `description` on product-card / quick-picks | 1–2 sentences that justify the pick | | `chips[]` | 1–3 words per chip, max 4 chips | | `quick_take` (pros-cons) | 1 sentence verdict | **Tone defaults**: editorial, second-person, specific. Avoid: "In today's world…", "When it comes to…", "game-changer", "dive in", "unlock", "seamless", "cutting-edge". No emojis unless user requests them. --- ## 8. Do-Not Checklist Read before generating. These are the most common ways output goes wrong. 1. **Do not** set `theme` or `color_scheme` on any block. Theme is global. 2. **Do not** hardcode CE-owned fields into any block: `url`, `img`, `price`, `priceOld`, `stock_status`, `logo`, `domain`, `last_update`, or merchant markup. 3. **Do not** invent block names, variants, or attributes. Emit **only** the fields listed in each block's schema (section 10). Do not guess that a field might exist because it sounds plausible — the block will silently ignore or break on unknown attributes. When uncertain whether a field exists, omit it. 4. **Do not** use paired `` form for any `eggb/*` block — all EggBlocks are self-closing `/-->`. (The one exception is `wp:paragraph`, which is a core block and does use paired form — see section 10's Core Blocks subsection.) 5. **Do not** emit empty strings, empty arrays, or zero-valued numbers unless the block explicitly requires them. 6. **Do not** set TOC metadata (`anchor`, `toc_label`, `include_in_toc`) on blocks unless an `eggb/toc` with `source_mode: "auto"` is part of the same article. 7. **Do not** run a multi-question interview. Infer from the prompt, state assumptions in the outline, let the user correct. 8. **Do not** write narration between blocks in the final deliverable. The article is the block sequence. 9. **Do not** use emojis in field content unless the user explicitly requests them. 10. **Do not** default to `items` for array fields. Most blocks use `items`, but two exceptions use different names: `eggb/specifications` uses **`specs`**, `eggb/step-list` uses **`steps`**. Always check the schema in section 10 before emitting — using the wrong field name produces an empty block. 11. **Do not** put prose, commentary, or editorial opinions in `eggb/specifications` `specs[].value`. That field is for factual data only (numbers, units, materials). Prose belongs in `key-takeaways`, `pros-cons`, or `verdict`. If you lack a factual value, omit the row. 12. **Do not** omit product blocks from product-oriented articles (reviews, roundups, buying guides, comparisons). These article types require at least one CE-bound block (`product-card`, `quick-picks`, `comparison-table`, `where-to-buy`, or `verdict`). **Missing `product_ref` is not a valid reason to skip.** Emit the block with the empty placeholder `{"module_id":"","unique_id":"","post_id":0}` and populated editorial fields — see section 6 for the exact pattern. 13. **Do not** use `wp:paragraph` when an EggBlock can carry the content. Check the block index (section 4) before reaching for a core paragraph — `callout`, `key-takeaways`, `section-header`, `methodology`, `intro`, and `conclusion` all have prose fields that cover common cases. `wp:paragraph` is a strict last resort for prose that genuinely fits no EggBlock field. --- ## 8.1 Self-Check Checklist (run before every delivery) For **every block** in your generated output, verify each item below. Fix violations before emitting. Do not skip this step even for single-block requests. ### A. Block identity - [ ] The block name (e.g. `eggb/faq`) exists in the Block Index (section 4). If not, replace it with the closest valid block. - [ ] The `variant` value is one of the exact strings listed in that block's schema in section 10. Variants are not open-ended — do not invent synonyms. ### B. Attribute validity - [ ] Every attribute key in your output appears in the block's schema in section 10. Remove any key that is not listed — no exceptions. - [ ] **Every array field has been cross-checked against the Array-Field Quick Reference (section 4.1).** Verify both the field name (e.g. `specs` vs `items`) and the item shape (string vs object, and which object keys). This is the single most common error class — do not skip. - [ ] No CE-owned fields are set: `url`, `img`, `price`, `priceOld`, `stock_status`, `logo`, `domain`, `last_update`. Remove them if present. - [ ] No `theme` or `color_scheme` attribute is set on any block. ### C. Required fields - [ ] `variant` is present on every `eggb/*` block. - [ ] CE-bound blocks (`product-card`, `quick-picks`, `comparison-table`, `where-to-buy`, and `verdict` when CE-linked) have `product_ref` on every item that needs it. Use the empty placeholder if no real ref is available — do not omit the field entirely. - [ ] `eggb/callout` has `callout_type` set. - [ ] `eggb/faq` items each have both `question` and `answer`. ### D. Serialization - [ ] Every `eggb/*` block uses self-closing form (`/-->`). No paired form for EggBlocks. - [ ] No literal newlines inside the JSON comment. Newlines inside string values are escaped as `\n`. - [ ] No trailing commas in JSON. - [ ] No empty strings, empty arrays, or `0`-valued numbers unless the schema explicitly requires them. ### E. Content rules - [ ] `eggb/specifications` `specs[].value` contains only factual data (numbers, units, materials) — no prose or opinion. - [ ] `wp:paragraph` is present only where no EggBlock field covers the content (check the lookup table in the Core Blocks section). If one does, replace the paragraph with the appropriate block or field. - [ ] Product-oriented articles (reviews, roundups, buying guides, comparisons) contain at least one CE-bound block. If you caught yourself thinking *"I don't have a product_ref, so I'll leave it out"* — add the block back with an empty `product_ref` placeholder (see section 6). Only after all checks pass: proceed to **Deliver** (step 5). --- ## 9. Shared Shapes ### 9.1 `product_ref` ```json { "module_id": "Amazon", "unique_id": "B09XXXXXXX", "post_id": 123 } ``` - `module_id` and `unique_id` required. - `post_id` optional; defaults to current post ID at render time. ### 9.2 TOC metadata (on supporting blocks) ```json { "anchor": "slug-id", "toc_label": "Label in TOC", "include_in_toc": true, "level": 2 } ``` - Set only when an `eggb/toc` block with `source_mode: "auto"` is in the article. - `anchor` becomes the wrapper HTML `id`. - `eggb/toc` auto mode collects only items where `include_in_toc: true` **and** both `anchor` and `toc_label` are non-empty. ### 9.3 Rich text Where a field is described as rich text, only a small safe HTML subset is rendered (basic inline, lists). Keep inline markup minimal. --- ## 10. Schema Reference Each entry: purpose, variants, CE data dependency, canonical attribute schema, and notes. Empty strings in schemas denote string fields with empty defaults — omit them from output unless you're setting a value. --- ### `eggb/callout` Editorial aside for a note, tip, warning, or insight adjacent to prose. **Variants** - `default` — standalone aside in article flow - `compact` — nested or space-tight usage **CE data**: none **Schema** ```json { "variant": "default | compact", "callout_type": "note | tip | warning | insight", "label_type": "", "title": "", "body": "" } ``` **Notes** - `callout_type` controls signal color, icon, and default label. - `title` is meaningful only in `default`. - `label_type` overrides the default label for `callout_type`; leave empty to use the default. --- ### `eggb/comparison-table` Multi-product comparison table with shared criteria. **Variants** - `default` — standard side-by-side comparison for 3+ products - `versus` — head-to-head comparison for exactly 2 products - `product-list` — dense quick-reference table where criteria become columns **CE data**: required, per row **Schema** ```json { "variant": "default | versus | product-list", "heading_label": "", "heading_title": "", "heading_tag": "div | h1 | h2 | h3 | h4", "cta_label": "", "footer_note": "", "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2, "items": [ { "id": "", "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 }, "title": "", "role_label": "", "is_winner": false } ], "criteria": [ { "key": "", "label": "", "type": "text | score | star | boolean | price", "values": [] } ] } ``` **Notes** - `items[].product_ref` is required for each usable row. - `criteria[].type = "price"` is CE-driven; `values` is ignored for that criterion. - `is_winner` applies to `default`; `versus` winner logic is criterion-driven. - `heading_tag` defaults to `"div"`; set to `h2`/`h3` for semantic output. --- ### `eggb/conclusion` Closing summary block with optional takeaway bullets and next-step links. **Variants** - `default` — full standalone article close - `compact` — short wrap-up inside nested or short-form contexts **CE data**: none **Schema** ```json { "variant": "default | compact", "section_label": "", "title": "", "heading_tag": "h2", "points": [""], "summary": "", "next_steps_label": "", "next_steps": [ { "text": "", "url": "" } ], "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - `summary` is the only required content field. - `title` is the large bold heading; `heading_tag` controls its element tag. - `next_steps[].url` must be a real URL, not `"#"`. --- ### `eggb/criteria` Buying-criteria guidance: what to prioritize, look for, and avoid. **Variants** - `default` — 2×2 panel treatment (works best with 4 criteria) - `list` — linear reading flow (works best with 3–6 criteria) **CE data**: none **Schema** ```json { "variant": "default | list", "section_label": "What to look for", "title": "", "heading_tag": "h1 | h2 | h3 | h4 | div", "criteria": [ { "title": "", "description": "", "importance": "high | medium | low", "look_for": "", "avoid": "" } ], "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - `importance` is semantic, not a styling input. - `heading_tag` is meaningful only when `title` is non-empty. --- ### `eggb/definitions` Glossary-style term/definition pairs for jargon, terminology, or spec explanations. **Variants** - `default` — row-card glossary - `compact` — lower-interruption inline glossary - `inline` — integrated prose-adjacent terminology list - `cards` — equal-weight 2-column grid **CE data**: none **Schema** ```json { "variant": "default | compact | inline | cards", "section_label": "Definitions", "title": "", "heading_tag": "h2", "items": [ { "term": "", "definition": "" } ] } ``` **Notes** - All variants including `inline` render the header when `section_label` or `title` is set. - Best kept to 3–6 items in most editorial contexts. --- ### `eggb/faq` Reader Q&A block for common questions and SEO-friendly answer coverage. **Variants** - `default` — collapsible accordion - `flat` — always-open static Q&A list **CE data**: none **Schema** ```json { "variant": "default | flat", "section_label": "Frequently Asked Questions", "title": "", "heading_tag": "h1 | h2 | h3 | h4 | div", "items": [ { "question": "", "answer": "" } ], "collapsed_by_default": false, "enable_schema": true, "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - Each item requires both `question` and `answer`. - `enable_schema` defaults to `true` and enables FAQPage JSON-LD; leave as-is unless the user has a reason to disable. --- ### `eggb/intro` Article-opening orientation block with lead framing and optional preview list. **Variants** - `default` — full-length article intro - `compact` — shorter intro where prose should stay tight **CE data**: none **Schema** ```json { "variant": "default | compact", "section_label": "", "title": "", "heading_tag": "h2", "lead": "", "body": "", "points_label": "", "points": [""], "cta_label": "", "cta_url": "", "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - `title` and `lead` are the core content. - `body` is supported in both variants (including `compact`). - `title` is the large bold heading; `heading_tag` controls its element tag. --- ### `eggb/key-takeaways` Concise editorial insights or conclusions, separate from product-spec data. **Variants** - `default` — standalone icon list - `compact` — nested or tight-column summary - `inline` — prose-adjacent quick list - `cards` — top-of-article or equal-weight takeaway grid **CE data**: none **Schema** ```json { "variant": "default | compact | inline | cards", "section_label": "Key Takeaways", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "items": [ { "text": "", "title": "" } ], "note": "", "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - `items[].title` is supported in all variants. - Avoid using this block for raw spec or commerce facts — use `specifications` or product blocks instead. --- ### `eggb/methodology` Explains how recommendations were evaluated to add credibility and transparency. **Variants** - `default` — parallel criteria list - `timeline` — ordered evaluation process - `grid` — compact 2×2 methodology overview (best with 4 items) **CE data**: none **Schema** ```json { "variant": "default | timeline | grid", "section_label": "", "title": "", "description": "", "items": [ { "icon": "", "title": "", "description": "" } ], "note": "", "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Variant-specific `items[]` shapes** - `default` and `timeline`: `{ "title": "", "description": "" }` - `grid`: `{ "icon": "", "title": "", "description": "" }` --- ### `eggb/myth-fact` Debunks misconceptions as myth/fact pairs or verdict-rated claims. **Variants** - `default` — full myth vs fact treatment with optional explanation row - `inline` — fast-scanning claim verdict list **CE data**: none **Schema** ```json { "variant": "default | inline", "section_label": "Myth vs Fact", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "label_myth": "", "label_fact": "", "label_why": "", "items": [ { "myth_text": "", "fact_text": "", "why_text": "", "verdict": "", "verdict_tone": "true | false | partial | neutral", "verdict_text": "" } ] } ``` **Notes** - `items` is the universal repeater for both variants. - `verdict_tone` controls badge semantics in `inline`. --- ### `eggb/product-card` Single CE-bound product recommendation card. **Variants** - `default` — standard recommendation card - `featured` — top-pick or lead recommendation - `compact` — lower-ranked scan-friendly row **CE data**: required **Schema** ```json { "variant": "default | featured | compact", "section_label": "", "block_title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 }, "title": "", "subtitle": "", "merchant": "", "badge": "", "rank": "", "score": "", "description": "", "chips": [""], "cta_label": "" } ``` **Notes** - `product_ref` is required for rendering. - `compact` hides `badge`, `score`, `subtitle`, `chips`, and `description`. - `section_label`, `block_title`, and `heading_tag` are block-level header fields — omit for the typical roundup-list usage; use only for standalone featured callouts. - Never set CE-owned fields (`url`, `img`, `price`, `logo`, etc.) here. --- ### `eggb/pros-cons` Structured strengths/weaknesses block for a product or recommendation. **Variants** - `default` — standalone review assessment - `compact` — nested inside shared layouts such as product sections - `highlight` — high-attention summary near article top - `inline` — minimal prose-adjacent aside **CE data**: none **Schema** ```json { "variant": "default | compact | highlight | inline", "pros": [""], "cons": [""], "best_for": [""], "not_for": [""], "quick_take": "", "label_pros": "", "label_cons": "", "label_best_for": "", "label_not_for": "", "label_quick_take": "" } ``` **Notes** - Canonical block key is `eggb/pros-cons`. - Content fields are `pros`, `cons`, `best_for`, `not_for`, `quick_take`. --- ### `eggb/quick-picks` CE-first multi-product shortlist block. **Variants** - `default` — ranked shortlist - `compact` — tighter ranked list - `alternatives` — "consider instead" set after a lead recommendation - `shelves` — grouped by use case rather than rank - `grid` — finalists matrix - `highlight` — lead pick plus supporting picks **CE data**: required, per row **Schema** ```json { "variant": "default | compact | alternatives | shelves | grid | highlight", "section_label": "Quick picks", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "cta_label": "", "items": [ { "id": "", "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 }, "title": "", "subtitle": "", "merchant": "", "badge": "", "description": "", "chips": [], "score": "" } ] } ``` **Notes** - `items[].product_ref` is required for each usable row. - Row order defines rank, featured behavior, and lead behavior. - `description`, `badge`, `score` are editorial overrides only — never live CE data. --- ### `eggb/rating-breakdown` Visual score breakdown for one product with overall and category scores. **Variants** - `default` — main review score breakdown - `compact` — space-constrained score view - `grid` — hero-score treatment with category grid (best with 6 categories; clamps to first 6) - `category-grid` — category-only scoring without overall score **CE data**: optional, editorial-only by default **Schema** ```json { "variant": "default | compact | grid | category-grid", "overall_score": "", "overall_denom": "out of 10", "stars": 0, "categories": [ { "label": "", "score": "" } ] } ``` **Notes** - `overall_score`, `overall_denom`, and `stars` are ignored in `category-grid`. - Scores assume a 0–10 scale. --- ### `eggb/related-posts` Internal navigation block linking to related articles. Use at article end, mid-article section breaks, or as a standalone "related reading" section. **Variants** - `compact` — text-only chevron list with optional snippets; end of article or tight spaces; 3–6 items - `media-list` — thumbnail + badge + title + excerpt rows; mid- or end-of-article; 3–5 items - `cards` — 2-column grid with cover images; standalone prominent section; 4 items recommended - `featured` — hero card (first item) + thumbnail list (remaining); 4–6 items **CE data**: none — items resolve from WordPress at render time via `post_id` **Schema** ```json { "variant": "compact | media-list | cards | featured", "section_label": "", "items": [ { "post_id": "123 or node-uuid", "title": "", "badge": "", "snippet": "" } ] } ``` **Notes** - `items[].post_id` accepts either a numeric WordPress post ID or a TMN `node_uuid` string (e.g. `1a93c132-454d-4310-a7fb-b73997c3881e`). - `title`, `badge`, `snippet` are optional per-item overrides; renderer falls back to WP post title, first category, and excerpt. - Scheduled posts (`future` WP status) render as plain text without a link. - Items with an unresolvable `post_id` or UUID are skipped silently. - Item order determines visual hierarchy; for `featured`, the first item becomes the hero card. --- ### `eggb/section-header` Named section opener for procedural steps or editorial framing before a grouped block. **Variants** - `default` — step header in a guide sequence - `accent` — stronger "Step N" treatment - `editorial` — framing header before lists, grids, or grouped recommendation blocks **CE data**: none **Schema** ```json { "variant": "default | accent | editorial", "step_number": 0, "title": "", "heading_tag": "h1 | h2 | h3 | h4 | div", "subtitle": "", "step_label_text": "", "kicker": "", "meta": "", "chips": [""], "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **Notes** - `title` is the core content field. - `step_number` is expected for `default` and `accent`. - `chips` are most useful in `editorial`. --- ### `eggb/specifications` Structured factual spec display for a product — numbers, units, materials, dimensions. **Not** for prose commentary, editorial opinions, or "why it's good" statements (use `key-takeaways`, `pros-cons`, or `verdict` for those). **Variants** - `default` — full spec grid with icons - `compact` — nested label/value table - `highlight` — at-a-glance stat band **CE data**: none **Schema** ```json { "variant": "default | compact | highlight", "section_label": "", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "specs": [ { "icon": "", "value": "", "label": "" } ] } ``` **⚠️ Field name is `specs`, NOT `items`.** This block is one of two exceptions (`step-list` uses `steps`). Using `items` will produce an empty block. **Value content rule.** `value` must be a factual datum — a number, a measurement, a material, a short fact. `label` is what that fact describes. ✅ Correct: ```json { "label": "Battery life", "value": "30 h (ANC on)" } { "label": "Weight", "value": "250 g" } { "label": "Drivers", "value": "30 mm dynamic" } { "label": "Codecs", "value": "LDAC, AAC, SBC" } ``` ❌ Wrong — prose commentary, not a spec: ```json { "label": "Battery life", "value": "A standout choice for long listening sessions" } { "label": "Sound", "value": "Rich, enjoyable tuning with broad appeal" } ``` If you don't have a factual value, **omit the row**. Don't invent one and don't substitute prose. **Other notes** - `specs[].icon` applies only to `default` variant; ignored by `compact` and `highlight`. - `section_label` defaults to "Key specs" in `default` when empty; empty by default in `compact` and `highlight`. - Header (`section_label` + `title`) is visible only in `default` — don't set them for `compact` or `highlight`, they won't render. --- ### `eggb/step-list` Ordered steps, checklist items, or scan-friendly instructional sequences. **Variants** - `default` — strict sequential process - `checklist` — completeness-focused tasks where order is advisory - `cards` — steps that need visual separation - `card-grid` — parallel-scanning overview **CE data**: none **Schema** ```json { "variant": "default | checklist | cards | card-grid", "section_label": "Step List", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "steps": [ { "title": "", "description": "" } ], "note": "", "anchor": "", "toc_label": "", "include_in_toc": false, "level": 2 } ``` **⚠️ Field name is `steps`, NOT `items`.** Using `items` will produce an empty block. **Notes** - Step numbers are derived from array order, not stored per item. - `description` is optional per step. --- ### `eggb/toc` Table of contents for anchor navigation within the article. **Variants** - `default` — standard TOC with optional sub-items - `compact` — dense flat TOC for many sections - `numbered` — sequence-oriented TOC for listicles or guides **CE data**: none **Schema** ```json { "variant": "default | compact | numbered", "label": "", "source_mode": "auto | manual", "items": [ { "text": "", "anchor": "", "sub_items": [ { "text": "", "anchor": "" } ] } ], "collapsible": true, "default_open": true } ``` **Notes** - `source_mode = "auto"` collects from TOC-enabled blocks (those with `include_in_toc: true` and non-empty `anchor` + `toc_label`). - `sub_items` are supported only in `default`. - When using `manual`, anchors must match actual article IDs. --- ### `eggb/verdict` Single-product editorial verdict with score, summary, and CTA. **Variants** - `default` — standard review conclusion block - `compact` — lighter-weight inline verdict - `summary` — full visual closing verdict **CE data**: optional (recommended when CTA should resolve through CE) **Schema** ```json { "variant": "default | compact | summary", "score": "", "score_denom": "/ 10", "score_label": "", "title": "", "award_label": "", "chips": [], "verdict_text": "", "cta_label": "", "cta_url": "", "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 }, "band_label": "" } ``` **Notes** - `score_label` and `band_label` are meaningful only in `summary`. - `chips` are short highlights, not prose. - Omit `product_ref` entirely if the verdict is not CE-bound. --- ### `eggb/where-to-buy` CE-backed multi-offer merchant block for buying options and price comparison. **Variants** - `default` — full multi-merchant comparison - `compact` — tighter offer list - `table-compact` — densest table layout **CE data**: required, per row **Schema** ```json { "variant": "default | compact | table-compact", "section_label": "Where to buy", "title": "", "heading_tag": "h2 | h3 | h4 | h1 | div", "cta_label": "", "footer_note": "", "items": [ { "id": "", "product_ref": { "module_id": "", "unique_id": "", "post_id": 0 }, "merchant": "", "title": "", "chips": [] } ] } ``` **Notes** - `items[].product_ref` is required for each usable offer row. - Only row-level editorial overrides are allowed. - Live price, stock, merchant output, CTA URL, and logos are CE-owned — never emit. --- ### Core Blocks This skill otherwise produces only `eggb/*` blocks. Two carve-outs: **`wp:paragraph`** — **strict last resort only.** Use only when prose genuinely cannot fit any EggBlock field. Before emitting, work through this checklist — if any of these covers the intent, use the EggBlock instead: | Content intent | Use instead | |---|---| | Article opener, lead-in | `eggb/intro` (`lead`, `body`) | | Short aside, tip, warning | `eggb/callout` (`body`) | | Insight bullets or summary | `eggb/key-takeaways` (`note` or `items`) | | Section framing before a block group | `eggb/section-header` (`subtitle`) | | Credibility / evaluation prose | `eggb/methodology` (`description`) | | Closing summary | `eggb/conclusion` (`summary`) | Only reach for `wp:paragraph` when the prose bridges two blocks and none of the above fits. Format: ```Your prose here.
``` - Paired form only. Inner HTML must be a single `` element. - Keep to 1–3 sentences. If more is needed, an EggBlock is the right answer. - No inline images, no headings, no lists inside the `