Feat/ricos author plugin shapes - #825
Open
jurasm wants to merge 12 commits into
Open
Conversation
Document BUTTON, AUDIO, VIDEO, GALLERY, COLLAPSIBLE_LIST, HTML, and SPOILER in the authoring reference, clarify BUTTON vs inline LINK, and add eval scenarios for link buttons and collapsible lists.
Explain that the renderer adds no margin between block nodes and add self-audit guidance for spacer placement after media, tables, and other blocks.
Contributor
❌ EvalForge YAML Gate: ErrorEval pipeline comparison failed |
The expanded authoring recipe increases ReadFullDocsArticle token usage; bump maxTokens so PR eval gate passes (table run ~409k, button ~242k).
Add routing rules in wix-manage SKILL and the author recipe so agents load the recipe before SearchWixAPISpec or convert APIs, and update rich-content eval trigger prompts to request that read explicitly.
Clarify when spacer paragraphs apply in minimal JSON outputs, add paragraphData to collapsible examples, and align eval judges accordingly.
…dia. Raise minScore on button/collapsible judges so prod cannot pass with missing buttonData.type or wrong COLLAPSIBLE_LIST_ITEM; add five evals for plugins only documented in the expanded Author Ricos recipe.
Drop the author-ricos doc URL from trigger prompts and rely on llm_judge only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands the Author Ricos Rich Content recipe so agents can hand-author more Ricos node types used in Blog, Stores, Events, and CMS rich-text fields — and documents how to get correct vertical spacing when rendering.
Plugin shapes added (
author-ricos-rich-content.md):LINKvsACTION; explicitly distinct from inlineLINKdecorations on TEXT_TITLE/_BODY→PARAGRAPH→TEXT)Also updates nesting rules, self-audit checklist, frontmatter description, and the
SKILL.mdindex entry.Vertical spacing — new section explaining that the renderer does not add margin between sibling block nodes; authors should insert empty
{ "type": "PARAGRAPH" }spacers after headings, between paragraphs, and after images, videos, tables, collapsible lists, buttons, and other blocks. Self-audit item #13 added.Eval scenarios (required coverage per CONTRIBUTING):
ricos-button.yml— CTA must be aBUTTONblock withbuttonData.type: "LINK", not an inline linkricos-collapsible-list.yml— correctCOLLAPSIBLE_LISTtitle/body nesting