@cyber-dash-tech/revela 0.18.14 → 0.18.16

package/plugins/revela/skills/revela-make-deck/SKILL.md

@@ -12,9 +12,10 @@ Use this skill when the user asks to make, generate, render, or update a Revela
 - Deck execution planning comes from canonical `deck-plan.md`.
 - Local materials, material reviews, `researches/`, `assets/`, and user intent provide source context.
 - Slide argument copy comes from `deck-plan.md` `Claim`, `Reasoning`, and `Audience takeaway` fields when present; raw findings are evidence/source context, not default body copy.
-- Active/requested design tools define valid layouts, slots, components, nesting hints, and HTML writing rules.
+- Active/requested design tools define valid layouts, slots, components, nesting hints, structure contracts, and HTML writing rules.
 - Active/requested domain guidance may inform communication framing, but it is not source evidence.
 - Generated artifacts live under `decks/*.html`.
+- After final Artifact QA passes, reply with the generated HTML deck as a standalone website link/card that opens in Codex Browser for native browsing and annotation.
 - Do not require a Narrative Vault before generating a deck.
 - This skill does not own normal plan authoring; `revela-research` owns source preparation and `deck-plan.md` planning handoff.
 - `deck-plan.md` is required for normal deck generation.
@@ -42,13 +43,14 @@ Before render preflight:
 1. Call `revela_design_list`.
 2. Call `revela_design_read` with `section: "rules"` for the active/requested design.
 3. Call `revela_design_inventory`.
+4. Review each component's `contract` field. Components with structure contracts must be planned from structured content and rendered with the required internal DOM/classes, not simplified freehand markup.
 
 Before HTML writing:
 
 1. Call `revela_read_deck_plan`.
 2. Read the returned `htmlWritingBatches`.
 3. Call `revela_design_read_layout` for each layout used in the current batch.
-4. Call `revela_design_read_component` for each component used in the current batch.
+4. Call `revela_design_read_component` for each component used in the current batch. For contract components, treat the returned CSS/HTML as executable grammar and preserve the required root, descendant, item, and alternating classes.
 5. Fetch chart rules before creating or modifying ECharts.
 
 ## Plan Preflight And Repair
@@ -81,12 +83,15 @@ Use this phase when the user asks to make, generate, render, or update an HTML d
 9. Preserve positive 1-based `data-slide-index` values.
 10. Every slide must have exactly one direct `.slide-canvas` child.
 11. Keep the HTML valid after each write.
-12. After every HTML write, call `revela_run_deck_qa` and repair hard errors before continuing, review, or export.
+12. After every HTML write, call `revela_run_deck_qa` and repair hard errors before continuing or export.
+13. After the final `revela_run_deck_qa` passes with zero hard errors, reply with a standalone Markdown link to the generated HTML deck artifact so Codex renders an Open in Browser website card.
+14. Prefer an absolute `file://` URL for the card. If the card or direct file navigation is unavailable, start a read-only local static server from the workspace root and use the exact `http://127.0.0.1:<port>/decks/<file>.html` URL.
 
 ## Outputs
 
 - `decks/*.html`.
 - Artifact QA status.
+- Website card/link for the QA-passed HTML deck.
 - Unresolved render/design issues and any plan diagnostics that require `revela-research` Planning Handoff.
 
 ## Must Not
@@ -96,6 +101,7 @@ Use this phase when the user asks to make, generate, render, or update an HTML d
 - Do not write a new `deck-plan.md` when it is missing.
 - Do not use design inventory names, slots, or components that were not returned by the active/requested design tools.
 - Do not use a slot that does not belong to the selected layout.
+- Do not hand-roll simplified internal DOM for contract components such as timelines. If the required structure cannot be satisfied, choose a simpler valid component or stop with the contract issue.
 - Do not patch more than 5 slide sections in one HTML write.
 - Do not invent source links, quotes, URLs, page references, caveats, or licenses.
 - Do not write remote image candidates directly into deck HTML; save them as workspace assets first.

package/plugins/revela/skills/revela-research/SKILL.md

@@ -49,6 +49,7 @@ Use this skill when the user asks to start from a goal, inspect local materials,
     - Call `revela_design_list`.
     - Call `revela_design_read` with `section: "rules"` for the active/requested design.
     - Call `revela_design_inventory`.
+    - When a chosen component has a `contract` field, preserve that contract in the visual brief/render notes so Make Deck renders the required internal structure instead of a simplified lookalike.
     - Write `deck-plan.md` directly from reviewed materials, saved findings, assets, user intent, active domain framing, and active design vocabulary.
     - Call `revela_read_deck_plan` after writing `deck-plan.md`.
     - If diagnostics report `sourceLinks`, layout, slot, component, or `children` issues, patch `deck-plan.md` directly and call `revela_read_deck_plan` again.

package/skill/SKILL.md

@@ -143,6 +143,9 @@ Rules for the slide plan:
 - Use exact layout names from the Layout Index and exact component names from
   the Component Index. Use only slots returned by the selected layout inventory.
   Do not invent layout, slot, or component names.
+- Components marked in the Component Index Contract column have mandatory
+  internal structure. Preserve their required DOM/classes in render notes and
+  HTML generation; do not describe them as generic visual ideas.
 - Use `box.children` when several child components support one semantic idea.
   Do not duplicate a child component both inside `box.children` and as a
   separate top-level component plan entry.
@@ -217,8 +220,11 @@ Before writing or materially changing HTML:
    layout names, comma-separated.
 5. Call `revela-designs` with `action: "read"` and `component` set to all
    required component names, comma-separated.
-6. Fetch `section: "chart-rules"` before using ECharts.
-7. Do not update legacy `requiredInputs`; design fetching is an execution step,
+6. For any component with a Contract marker, copy the fetched component
+   structure closely and keep its required root, descendant, item, and
+   alternating classes.
+7. Fetch `section: "chart-rules"` before using ECharts.
+8. Do not update legacy `requiredInputs`; design fetching is an execution step,
    not a workflow permission gate.
 
 Never generate HTML from memory or prior knowledge of a design. Copy the fetched
@@ -279,6 +285,9 @@ The active design defines a closed vocabulary of layouts and components.
 
 - Every slide must use exactly one layout class from the Layout Index.
 - Every content block must use component classes from the Component Index.
+- Contract components must satisfy their fetched structure contract. Do not
+  replace a timeline, roadmap, chart frame, or other structured component with
+  a visual approximation that only resembles it.
 - Do not invent layout classes, component names, CSS variables, custom grids, or
   custom visual effects.
 - Do not define new class rules in the deck `<style>` block unless the fetched

package/plugins/revela/skills/revela-review/SKILL.md

@@ -1,46 +0,0 @@
----
-name: revela-review
-description: Open the Revela Review UI or read deck diagnostics for generated HTML deck artifacts in Codex.
----
-
-# Revela Review
-
-Use this skill when the user asks to review, diagnose, QA, or refine a generated Revela deck.
-
-## Contract
-
-- Review is the post-artifact surface for generated `decks/*.html`.
-- A plain review request opens the Review UI.
-- Diagnostics are read explicitly when the user asks for QA details, export readiness, or no-GUI output.
-- Review UI is QA + Leave Comment / Apply. Insight/Inspect is removed from the public Review path.
-
-## Preconditions
-
-- A target `decks/*.html` file exists.
-- If multiple deck candidates exist and the user did not specify one, choose the most recent or most clearly requested deck and state the choice.
-
-## Inputs
-
-- HTML deck path.
-- Optional user review/refine intent.
-
-## Workflow
-
-1. Resolve the target `decks/*.html` file from the user request or unambiguous workspace state.
-2. For a plain review request, call `revela_review_deck_open` and let the tool open the browser by default.
-3. Use `revela_review_deck_read`, normally with `format: "markdown"`, only when the user explicitly asks for diagnostics, QA details, export readiness, or no-GUI output.
-4. Do not call `revela_run_deck_qa` separately for a normal Review UI open.
-5. Pure visual/layout/export fixes may patch artifacts directly when the user asks for a change, but read active design rules first with `revela_design_read` using `section: "rules"`.
-6. Content changes that affect the deck argument should update `deck-plan.md` first, then remake the deck.
-
-## Outputs
-
-- Review UI URL/open state.
-- Or Markdown/JSON diagnostics and current readiness summary.
-
-## QA Notes
-
-- `revela_review_deck_read` is read-only: it must not mutate deck HTML, `deck-plan.md`, assets, or compatibility state.
-- `revela_review_deck_open` returns URL/token/open state and basic file metadata.
-- Repair hard QA errors before treating a deck as review-ready.
-- Deck slides must use `<section class="slide" ...>` with exactly one direct `.slide-canvas` child.