@cyber-dash-tech/revela 0.1.2 → 0.1.3

package/skill/SKILL.md

@@ -136,8 +136,9 @@ Each axis gets its own dedicated agent with a focused brief. Launch ALL agents
 in a single message (parallel Task tool calls).
 
 **How to decompose:** Look at what the presentation needs to cover. Each major
-entity, comparison dimension, or macro question is a separate axis. Typical
-decompositions:
+entity, comparison dimension, or macro question is a separate axis. Decompose
+based on topic breadth and the depth each axis warrants — a narrow topic may
+need 2 axes; a complex comparison may need 4 or more. Typical decompositions:
 
 | Topic type | Example axes |
 |---|---|
@@ -146,38 +147,7 @@ decompositions:
 | Investment thesis | Opportunity metrics, risk factors, comparable deals, macro trends |
 | Product strategy | User research, competitor features, technology feasibility, go-to-market |
 
-**3+ axes → 3+ parallel agents.** Never collapse everything into one brief.
-
-##### Invocation Example — Multi-Agent Parallel
-
-For a topic like "Investment shift from OpenAI to Anthropic":
-
-```
-Agent 1 (Anthropic):
-> Research Anthropic's trajectory for a presentation on AI investment shifts:
-> - Funding history: Series rounds, valuations, key investors
-> - Revenue and growth: run-rate, enterprise adoption, key products
-> - Competitive advantages: safety positioning, developer tools, reliability
-> Focus on 2025-2026 data. Write findings to researches/ai-investment-shift/
-
-Agent 2 (OpenAI):
-> Research OpenAI's challenges for a presentation on AI investment shifts:
-> - Financial: burn rate, profitability timeline, cost structure
-> - Operational: API reliability data, outage frequency, enterprise complaints
-> - Governance: nonprofit conversion, leadership controversies, investor concerns
-> Focus on 2025-2026 data. Write findings to researches/ai-investment-shift/
-
-Agent 3 (Market & Capital Flow):
-> Research AI industry capital flow for a presentation on AI investment shifts:
-> - VC investment patterns: dual-backing trends, secondary market activity
-> - Enterprise adoption: market share shifts, switching patterns
-> - Macro trends: agentic AI adoption, market size projections
-> Focus on 2025-2026 data. Write findings to researches/ai-investment-shift/
-```
-
-Launch all agents in **one message** using parallel Task tool calls. Each agent
-runs independently and writes its own findings file:
-`researches/{topic-slug}/{axis-name}.md`
+Launch ALL agents in a single message (parallel Task tool calls).
 
 Each agent's brief should specify:
 - The topic slug (shared, e.g. `ai-investment-shift`)
@@ -192,20 +162,9 @@ each `.md` file. Each file contains structured `## Data`, `## Cases`,
 Cross-reference agent findings with workspace documents (Layer 1). Flag any
 contradictions.
 
-##### Fallback — ONLY if Research Agent is Unavailable
-
-If and only if the Task tool with `subagent_type: "revela-research"` is **not
-available as a tool** (i.e., it does not exist in your tool list), fall back to
-using `webfetch` directly on targeted URLs. Even in fallback mode, structure
-your research by axis — do not run a single vague query.
-
-Note: `websearch` is blocked by the Revela plugin when agents are available.
-In fallback mode, use `webfetch` with specific URLs from your knowledge.
-
 **Anti-pattern — NEVER do this:**
-- Do NOT use `websearch` directly — it is blocked by the Revela plugin to
-  enforce systematic research. Use research agents (or `webfetch` for specific
-  URLs in fallback mode).
+- Do NOT use `websearch` directly — it is blocked by the Revela plugin;
+  use research agents instead.
 - Do NOT run a few quick searches, decide "that's enough data", and skip the
   research agent. The agent's job is deep, systematic research — ad-hoc
   fetches cannot replace it.
@@ -273,13 +232,15 @@ A 6-slide deck might be: Cover → Background → Content × 3 → Closing.
 An 8-slide deck might be: Cover → TOC → Background → Content × 3 → Summary → Closing.
 Never skip Cover, Background, or Closing regardless of slide count.
 
-**Every `<section class="slide">` must include a `data-slide-type` attribute** declaring its structural role:
+**Every `<section class="slide">` must include a `slide-qa` attribute.** Set
+`slide-qa="true"` for content-heavy layouts (those marked ✓ in the Layout Index
+QA column of the active design). Set `slide-qa="false"` for structural or sparse
+layouts (cover, TOC, closing, quote, summary, etc.). When unsure, use `"false"`.
 
-<!-- @slide-types -->
+Example: `<section class="slide" slide-qa="true" data-index="0">`
 
-Example: `<section class="slide" data-slide-type="cover" data-index="0">`
-
-The layout QA system uses this to skip fill-ratio and spacing checks on structural slides that are intentionally sparse.
+The layout QA system uses this to skip fill-ratio and spacing checks on slides
+that are intentionally sparse.
 
 ### Domain Context
 
@@ -342,96 +303,17 @@ Follow these rules on every generation. They are non-negotiable.
 
 ### Inline Editing
 
-**Always include inline editing** in every generated presentation. This enables
-users to click any text element and edit it directly in the browser, then
-export the changes.
-
-Implementation rules:
-
-- **JS-based hover activation** — attach `mouseenter` / `mouseleave` listeners
-  on editable elements. After a 400ms hover delay, show a subtle outline to
-  indicate editability. Click activates `contenteditable`. Click outside or
-  press Escape to deactivate.
-- **Never** use CSS `~` sibling selector (breaks due to `pointer-events: none`
-  interrupting the hover chain).
-- **Editable elements** — only text content: `h1, h2, h3, h4, p, span, li,
-  blockquote, cite` and design-specific text classes (`.card-title`, `.card-body`,
-  `.stat-number`, `.stat-label`, `.stat-desc`, `.step-title`, `.step-desc`).
-  Never make structural containers or images editable.
-- **Hover style** — `outline: 1px dashed rgba(128,128,128,0.3)` on hover,
-  `outline: 2px solid rgba(59,130,246,0.5)` when actively editing. Keep it
-  subtle — must not interfere with the design aesthetic.
-- **`window.getEditedHTML()`** — always define this global function. It returns
-  the full edited HTML (`'<!DOCTYPE html>\n' + document.documentElement.outerHTML`).
-  The parent frame calls this to retrieve the full edited HTML for saving.
-
-Reference implementation (include in the `<script>` block after `SlidePresentation`):
-
-```javascript
-// --- Inline Editing ---
-(function() {
-    const EDITABLE = 'h1,h2,h3,h4,p,span,li,blockquote,cite,' +
-        '.card-title,.card-body,.stat-number,.stat-label,.stat-desc,' +
-        '.step-title,.step-desc';
-    let hoverTimer = null;
-    let activeEl = null;
-
-    document.querySelectorAll(EDITABLE).forEach(el => {
-        el.addEventListener('mouseenter', () => {
-            hoverTimer = setTimeout(() => {
-                el.style.outline = '1px dashed rgba(128,128,128,0.3)';
-                el.style.cursor = 'text';
-            }, 400);
-        });
-        el.addEventListener('mouseleave', () => {
-            clearTimeout(hoverTimer);
-            if (el !== activeEl) {
-                el.style.outline = '';
-                el.style.cursor = '';
-            }
-        });
-        el.addEventListener('click', (e) => {
-            if (activeEl && activeEl !== el) {
-                activeEl.contentEditable = 'false';
-                activeEl.style.outline = '';
-                activeEl.style.cursor = '';
-            }
-            el.contentEditable = 'true';
-            el.style.outline = '2px solid rgba(59,130,246,0.5)';
-            el.style.cursor = 'text';
-            activeEl = el;
-            e.stopPropagation();
-        });
-    });
-
-    document.addEventListener('click', () => {
-        if (activeEl) {
-            activeEl.contentEditable = 'false';
-            activeEl.style.outline = '';
-            activeEl.style.cursor = '';
-            activeEl = null;
-        }
-    });
-    document.addEventListener('keydown', (e) => {
-        if (e.key === 'Escape' && activeEl) {
-            activeEl.contentEditable = 'false';
-            activeEl.style.outline = '';
-            activeEl.style.cursor = '';
-            activeEl = null;
-        }
-    });
-
-    window.getEditedHTML = () =>
-        '<!DOCTYPE html>\n' + document.documentElement.outerHTML;
-})();
-```
+**Always include inline editing** in every generated presentation. The complete
+reference implementation is provided in the active design's `@design:foundation`
+section. Follow it exactly — pay attention to the hover-delay pattern, editable
+element selector list, and `window.getEditedHTML()` definition.
 
 ### Image Rules
 
 - Use direct file paths (`src="assets/logo.png"`) in HTML — not base64
 - Always use the **original** file path in HTML `<img src>` for full-quality rendering
 - Never repeat the same image on multiple slides (logos: title + closing only)
-- Image compression is handled automatically by the server (see File Access Rules below)
+- Image compression is handled automatically by the server
 - **Use the active design's image components** (`.image-card`, `.card-img`, `.avatar`)
   for displaying images — they provide proper rounded corners and cropping
 
@@ -615,62 +497,4 @@ The active design name is in the HTML comment at the top of this prompt:
 The active design's complete visual specification — Component Library, Layout
 Primitives, Composition Guide, and Data Visualization rules — is injected
 below after the `---` separator. This is your sole visual reference for
-generating slides.
-
----
-
-## What Comes Next in This System Prompt
-
-After the `---` separators below, two additional sections may appear:
-
-1. **Domain definition** (if a domain other than "general" is active) — report
-   structure, AI logic rules, terminology, and visual preferences for the domain.
-2. **Visual style** (from the active design) — colors, fonts, animation specifics,
-   layout variants. Apply it precisely — it overrides any default aesthetic preferences.
-
-If only one `---` section follows, it is the visual style (no domain is active).
-
----
-
-## File Access Rules
-
-### How tools interact with files
-
-The workspace `.ignore` file prevents binary formats from appearing in `grep`,
-`glob`, and `list` results (these tools use ripgrep, which honours `.ignore`).
-The `read` tool works by **direct file path** and is **not** affected by
-`.ignore` — if you have a path, you can always `read` it.
-
-### Documents
-
-`.pdf` `.xlsx` `.xls` `.docx` `.doc` `.pptx` `.ppt` `.csv`
-
-If the `extract` tool is available, use it to extract document content as clean
-markdown text. **NEVER** use the `read` tool on PDF, Excel, Word, or PPT files
-— their raw binary content will flood the context window.
-
-If the `extract` tool is NOT available, use `read` only for text-based formats
-(`.csv`, plain text). For binary document formats, inform the user and ask them
-to provide the content in text form.
-
-### Images
-
-`.png` `.jpg` `.jpeg` `.gif` `.webp` `.bmp` `.tiff` `.tif` `.avif`
-
-Use the `read` tool to view images directly (OpenCode returns them as visual
-attachments). In HTML, always reference the original file path for full-quality
-rendering:
-
-```html
-<img src="photos/screenshot.png" alt="...">
-```
-
-### Binary files — never access
-
-These are excluded from all tools:
-
-`.mp4` `.mov` `.avi` `.mkv` `.webm` `.m4v` `.wmv`
-`.mp3` `.wav` `.ogg` `.flac` `.aac` `.m4a`
-`.zip` `.tar` `.gz` `.bz2` `.7z` `.rar` `.tgz`
-`.woff` `.woff2` `.ttf` `.otf` `.eot`
-`.db` `.sqlite` `.sqlite3` `.bin` `.exe` `.dll` `.so` `.dylib`
+generating slides.

package/tools/designs.ts

@@ -7,8 +7,10 @@ import {
   removeDesign,
   parseDesignSections,
   generateComponentIndex,
+  generateLayoutIndex,
   getDesignSection,
   getDesignComponent,
+  getDesignLayout,
 } from "../lib/design/designs"
 import { buildPrompt } from "../lib/prompt-builder"
 import { existsSync, readFileSync } from "fs"
@@ -23,7 +25,7 @@ export default tool({
     "Use action 'activate' to switch to a different design (requires name). " +
     "Use action 'install' to add a new design from a URL, local path, or github:user/repo shorthand (requires source). " +
     "Use action 'remove' to uninstall a design (requires name). " +
-    "Use action 'read' to fetch on-demand design content: pass component (comma-separated names) to get full CSS/HTML for specific components, or section ('charts' | 'guide' | 'global' | 'layouts' | 'components') to get an entire section. Pass neither to get the Component Index table. " +
+    "Use action 'read' to fetch on-demand design content: pass layout (comma-separated names) to get full HTML/CSS for specific layouts, pass component (comma-separated names) to get full CSS/HTML for specific components, or section ('chart-rules' | 'foundation' | 'layouts' | 'components') to get an entire section. Pass neither to get the Component Index table. " +
     "After activating a new design, the system prompt is automatically rebuilt.",
   args: {
     action: tool.schema
@@ -39,6 +41,12 @@ export default tool({
       .describe(
         "Install source — URL, local path, github:user/repo. Required for install."
       ),
+    layout: tool.schema
+      .string()
+      .optional()
+      .describe(
+        "For action 'read': comma-separated layout name(s) to fetch (e.g. 'cover', 'two-col,card-grid')"
+      ),
     component: tool.schema
       .string()
       .optional()
@@ -49,7 +57,7 @@ export default tool({
       .string()
       .optional()
       .describe(
-        "For action 'read': section name to fetch — 'charts', 'guide', 'global', 'layouts', or 'components'"
+        "For action 'read': section name to fetch — 'chart-rules', 'foundation', 'rules', 'layouts', or 'components'"
       ),
   },
   async execute(args) {
@@ -96,13 +104,18 @@ export default tool({
           }
           const raw = readFileSync(mdPath, "utf-8")
           const { body } = parseFrontmatter(raw)
-          const { components, hasMarkers } = parseDesignSections(body)
+          const { layouts, components, hasMarkers } = parseDesignSections(body)
 
           if (!hasMarkers) {
             // No markers — return full body
             return body
           }
 
+          // Specific layout(s) requested
+          if (args.layout) {
+            return getDesignLayout(args.layout, designName)
+          }
+
           // Specific component(s) requested
           if (args.component) {
             return getDesignComponent(args.component, designName)
@@ -113,8 +126,11 @@ export default tool({
             return getDesignSection(args.section, designName)
           }
 
-          // Default: return Component Index
-          return generateComponentIndex(components)
+          // Default: return Layout Index + Component Index
+          const li = generateLayoutIndex(layouts)
+          const ci = generateComponentIndex(components)
+          const parts = [li, ci].filter(Boolean)
+          return parts.join("\n\n---\n\n") || "(no layouts or components found)"
         }
         default:
           return JSON.stringify({ error: `Unknown action: ${args.action}` })