@cyber-dash-tech/revela 0.1.0

package/domains/consulting/INDUSTRY.md

@@ -0,0 +1,230 @@
+---
+name: consulting
+description: Strategic consulting reports — Go/No-Go decisions, Strategy Design, Belief Change
+author: revela
+version: 1.0.0
+---
+
+# Strategic Consulting Reports — Domain Knowledge
+
+## 1. Core Definition
+
+This domain covers three canonical consulting report types. The reasoning core is:
+**Claim → Evidence → Synthesis**, executed under imperfect information.
+Every conclusion must be earned through evidence, never asserted by adjective.
+
+### Report Type Auto-Detection
+
+| Signal in User Request | Report Type |
+|------------------------|-------------|
+| "Should we enter / invest / do X?" / "Is X worth doing?" | **Type I: Go/No-Go** |
+| "How should we do X?" / "Which path?" / "What strategy?" | **Type II: Strategy Design** |
+| "We believe X, is that right?" / "Help us rethink X" | **Type III: Belief Change** |
+| Unclear | Ask the user before starting |
+
+---
+
+## 2. Unified Argumentation Protocol
+
+Execute these four steps internally before writing any slide content.
+
+### Step 1: Claims
+
+Convert every question into a declarative judgment: not "Is the market growing?" but
+"The market is in sustained growth phase." Every slide title follows the same rule.
+
+### Step 2: Evidence Plan
+
+For each claim, identify required evidence types before collecting:
+TAM / CAGR / demand drivers / capital flow / policy / company financials / case studies.
+
+### Step 3: Evidence Collection — Priority Ladder
+
+| Level | Type | Use when |
+|-------|------|----------|
+| L1 | Direct data (financials, market studies) | Always preferred |
+| L2 | Indirect indicators (capex, volumes, hiring) | L1 unavailable |
+| L3 | Named case studies (company + outcome) | Corroborate or illustrate |
+| L4 | Logical inference / first principles | Last resort only |
+
+Auto-downgrade when higher levels are unavailable. **Never interrupt reasoning.**
+
+### Step 4: Synthesis
+
+```
+Claim → Evidence (≥2 types) → Logic (causal link) → Conclusion
+```
+
+Every claim needs ≥2 different evidence types. Every slide: 1 core insight + 3–5 supporting points + ≥1 evidence.
+
+---
+
+## 3. Report Type I: Go / No-Go
+
+**Goal:** Clear Yes / No / Conditional verdict on whether a strategic action is worth taking.
+
+### Slide Structure (20–30 pages)
+
+| Slide | Title | Content |
+|-------|-------|---------|
+| P1 | Executive Answer | Verdict + 3 core reasons (≤2 sentences each) |
+| P2 | Key Risks Up Front | Top 3 risks (surfaces credibility early) |
+| P3 | Scope & Framing | What is being evaluated; key constraints and assumptions |
+| P4–P6 | Opportunity: Market Size | TAM/SAM/SOM; growth rate; addressable segment |
+| P7–P9 | Opportunity: Demand Drivers | 2–3 structural drivers with evidence; timeline |
+| P10–P12 | Economics: Revenue Model | Revenue structure; benchmark margins; how money is made |
+| P13–P15 | Economics: Cost Structure | Key cost drivers; unit economics; comparable cases |
+| P16–P17 | Entry Requirements: Capabilities | Capability threshold; current gap assessment |
+| P18–P19 | Entry Requirements: Resources | Capital, time, partnerships required |
+| P20–P22 | Risk Deep Dive | Market / Competitive / Execution / External risk |
+| P23–P24 | Scenarios | Best / Base / Worst with quantified outcomes and triggers |
+| P25–P27 | Competitive Landscape | Who is here; their advantages; whitespace |
+| P28 | Opportunity Cost | What is forgone either way |
+| P29 | Conditions for Yes | 3–5 conditions that must hold for success |
+| P30 | Final Recommendation | Decision + rationale + next action |
+
+### Page Allocation
+
+| Requested | Strategy |
+|-----------|----------|
+| ≤10 | Verdict (P1) + Opportunity condensed (1) + Economics (1) + Risks (1) + Recommendation (P30) |
+| 10–20 | All 7 sections; 1–2 slides each; skip scenario detail |
+| 20–30 | Full structure above |
+| >30 | Expand evidence slides; add data appendix |
+
+---
+
+## 4. Report Type II: Strategy Design
+
+**Goal:** Identify the best strategic path among alternatives. Delivers a recommended option with execution plan.
+
+### Slide Structure (20–30 pages)
+
+| Slide | Title | Content |
+|-------|-------|---------|
+| P1 | Recommended Path | Answer upfront: which option + why (2 sentences) |
+| P2 | Objective & Constraints | Strategic goal + non-negotiable constraints + success metrics |
+| P3 | Framing the Choice | Options available; how analysis is structured |
+| P4–P6 | Value Pool Analysis | Where profit concentrates in the value chain; distribution evidence |
+| P7–P9 | Competitive Landscape | Market structure; competitive dynamics; moats |
+| P10–P11 | Capability Fit | Current capabilities vs. path requirements; gap map |
+| P12–P14 | Option A | What it is + how it works + evidence it can succeed |
+| P15–P17 | Option B | Same structure |
+| P18 | Option C (if applicable) | Same structure, condensed |
+| P19–P21 | Option Comparison Matrix | Return / difficulty / risk / capability fit / timeline |
+| P22–P23 | Risks of Recommended Path | Top 3 risks + mitigation |
+| P24 | Build / Partner / Acquire | How to close capability gaps |
+| P25–P27 | Execution Plan | Phase 1/2/3 milestones; resources; decision gates |
+| P28 | Success Metrics | 3–5 KPIs with targets and cadence |
+| P29 | Downside Scenario | If recommended path fails; fallback |
+| P30 | Decision & Next Steps | Confirm recommendation + immediate actions (owner + timeline) |
+
+### Page Allocation
+
+| Requested | Strategy |
+|-----------|----------|
+| ≤10 | Recommendation (P1) + Value Pool (1) + Options A/B comparison (2) + Execution (1) + Decision (1) |
+| 10–20 | All sections; 1 slide per option; 1-slide execution summary |
+| 20–30 | Full structure above |
+| >30 | Expand each option; add financial modeling appendix |
+
+---
+
+## 5. Report Type III: Belief Change
+
+**Goal:** Shift a decision-maker's mental model. Persuasion through evidence and reframing, not assertion.
+
+### Slide Structure (20–30 pages)
+
+| Slide | Title | Content |
+|-------|-------|---------|
+| P1 | The New Frame | One sentence: the new belief. The whole deck proves this. |
+| P2 | What We Used to Believe | Articulate the current belief honestly — earn trust before challenging |
+| P3 | Why That Belief Made Sense | Validate the old model; show when it was correct |
+| P4–P6 | The Gap / Tension | Evidence the old belief can no longer explain current observations |
+| P7–P9 | Breaking the Old Frame | 3 specific pieces of evidence directly contradicting the old belief |
+| P10–P12 | The New Frame Explained | What the new model is; how it explains the gaps |
+| P13–P15 | Proof: Benchmark Companies | 2–3 named companies operating under the new frame — with outcomes |
+| P16–P17 | Proof: Edge Cases | Cases where the old belief led to demonstrably wrong decisions |
+| P18–P19 | Proof: Quantitative Evidence | Market data or research validating the new frame |
+| P20–P21 | Implication: Opportunity | What becomes possible under the new frame |
+| P22–P23 | Implication: Risk of Not Changing | What is at stake if the old belief persists |
+| P24–P25 | The Stakes | Quantify: acting on old frame vs. new frame |
+| P26–P27 | Objection Handling | Top 3 objections + direct rebuttals with evidence |
+| P28 | What This Means for Us | Specific implications for the audience's context |
+| P29 | Action Direction | 2–3 strategic directions enabled by the new frame |
+| P30 | The Ask | What you want the audience to believe / decide / do next |
+
+### Page Allocation
+
+| Requested | Strategy |
+|-----------|----------|
+| ≤10 | Old belief (P2) + Gap (P4) + Break (P7) + New Frame (P10) + Proof (P13) + Implication (P20) + Ask (P30) |
+| 10–20 | All 8 sections; compress proof to 2 slides; merge or skip objection handling |
+| 20–30 | Full structure above |
+| >30 | Expand proof with additional cases; add data appendix |
+
+---
+
+## 6. Research Guidance
+
+### Information Mapping
+
+| Document Type | Map to Report Section |
+|---------------|-----------------------|
+| Market research reports | Opportunity (Type I P4–P9), Value Pool (Type II P4–P6) |
+| Company financials / P&L | Economics (Type I P10–P15), Option analysis (Type II) |
+| Competitor analysis | Competitive Landscape, Option comparison |
+| Internal strategy docs | Constraints, Capability fit, Objectives |
+| Case study materials | Proof slides (Type III), Case evidence (all types) |
+| Interview / meeting notes | Risk identification, Constraints, Belief mapping (Type III) |
+| Industry news / press | Demand drivers, Policy signals, Competitive dynamics |
+
+### Cross-Source Conflict Handling
+
+- **User document vs. AI knowledge:** User document takes precedence
+- **Two user documents conflict:** Flag in the relevant risk slide:
+  `[Data Conflict: Source A shows X; Source B shows Y — reconciliation needed]`
+- **Missing data:** Auto-downgrade to L3/L4 evidence. Never halt.
+
+---
+
+## 7. AI Logic Engine Directives
+
+### Conclusive Title Rule
+
+Every slide title is the insight — a conclusion, not a label:
+
+| Correct | Wrong |
+|---------|-------|
+| "Market growing at 18% CAGR — entry window is open" | "Market Overview" |
+| "Path B requires capabilities we do not currently have" | "Option Comparison" |
+| "All three benchmark leaders chose vertical integration" | "Competitive Landscape" |
+
+### Evidence Attribution
+
+Cite source inline for all critical data: `[Source: McKinsey, 2023]`, `[Source: Company 10-K FY2023 p.47]`,
+`[Source: analytical inference — verify]`. No unsourced assertions on key claims.
+
+### Signal-to-Noise Rule
+
+Never use without quantitative backing: "leading", "dominant", "significant", "transformative",
+"clearly", "obviously". Replace with specifics: not "significant opportunity" but
+"$4.2B market growing at 18% CAGR (2023–2028)".
+
+### Structural Defaults
+
+- **2×2 matrices** for positioning comparisons (risk vs. return, capability vs. attractiveness)
+- **Comparison tables** mandatory in Type II; ≥3 evaluation dimensions
+- **Before/After frames** mandatory in Type III for old vs. new belief visualization
+- **If request spans Type I + II:** complete Type I verdict first; proceed to Type II only if verdict is Go or Conditional
+
+---
+
+## 8. Visual Preferences (Advisory — Design Layer Takes Priority)
+
+- **Tone:** Clean, high-contrast, professional. Dark text on light background.
+- **Layout:** Prioritize matrices, comparison tables, and side-by-side layouts over bullet lists
+- **Color:** Neutral (gray/blue) for facts; amber for opportunity; red for risk. One accent per slide.
+- **Density:** Medium-high — consulting slides carry more data than pitch decks
+- **Annotation:** Call out key figures with stat-card or pull-quote; do not bury in table cells

package/domains/deeptech-investment/INDUSTRY.md

@@ -0,0 +1,160 @@
+---
+name: deeptech-investment
+description: 硬科技投资行业——半导体、量子计算、核能、新能源、创新药等投研报告
+author: slides-it
+version: 1.0.0
+---
+
+# 硬科技投资 — 行业定义
+
+## 1. 核心定义 (Definition)
+
+本场景专为硬科技（半导体、量子计算、核能、新能源、创新药等）投资经理设计。
+逻辑重心在于**"从底层科学证实向商业工程化落地"的收敛**。
+对于早期项目，自动切换为"学术溯源"与"第一性原理"权重模式。
+
+## 2. 报告结构框架 (30-Page Framework)
+
+**本结构覆盖 SKILL.md 中的 Required Slide Structure。** 生成硬科技投研报告时，
+按以下五阶段组织内容。用户请求的 slide 数量决定每阶段的详略分配。
+
+### 第一阶段：执行摘要与核心逻辑 (P1-P3)
+
+| Page | 标题 | 内容 |
+|------|------|------|
+| P1 | 执行摘要 (The Big Idea) | 突破性技术名称 + 解决的底层物理/化学痛点 + 预估商业天花板。提炼该技术如何打破行业"不可能三角"的逻辑。 |
+| P2 | 投资亮点 (Investment Thesis) | 3 条核心理由（如：技术独占性、全球唯一量产工艺、顶级科学家背书）。 |
+| P3 | 关键风险 (Killer Risks) | 识别技术迭代风险、工艺瓶颈、核心人物离职风险。 |
+
+### 第二阶段：底层科学与学术护城河 (P4-P10)
+
+| Page | 标题 | 内容 |
+|------|------|------|
+| P4-P5 | 第一性原理 (The Science) | 将论文/专利转化为原理图，说明在分子/原子/电子层面的先进性。 |
+| P6-P7 | 学术谱系 (Academic Lineage) | 创始人导师、所属国家重点实验室、H-index、顶级期刊（Nature/Science）发表记录。**早期项目核心**——判定技术正统性与学术圈层资源。 |
+| P8-P10 | 专利与 IP (IP Moat) | 统计底层专利 vs 应用专利、地域保护、到期时间、职务发明洁净度。 |
+
+### 第三阶段：硬核参数对比与实验证据 (P11-P18)
+
+| Page | 标题 | 内容 |
+|------|------|------|
+| P11-P13 | 性能对标 (Benchmarking) | 提取 Top 3 关键指标（如：Qubit 数量、转化效率、药代动力学参数）。对比逻辑：[本项目] vs [行业龙头 Tier 1] vs [学术界基准]。 |
+| P14-P18 | 数据验证 (Data Evidence) | 识别良率曲线、P 值、置信区间或临床 Endpoint。 |
+
+### 第四阶段：工程化路径与市场 (P19-P25)
+
+| Page | 标题 | 内容 |
+|------|------|------|
+| P19-P21 | TRL 评估 (Scalability) | 评估 TRL 1-9 阶段。分析从实验室（Lab）到中试（Pilot）的转化瓶颈。 |
+| P22-P25 | 行业拐点 (Market Dynamics) | 分析政策红利、国产替代空间或新市场增量。 |
+
+### 第五阶段：交易结构与决策 (P26-P30)
+
+| Page | 标题 | 内容 |
+|------|------|------|
+| P26 | 股权结构 (Cap Table) | 创始人、员工持股平台、过往投资方及其持股比例。 |
+| P27 | 融资方案 (The Deal) | 拟融资金额、投前/投后估值、融资用途。 |
+| P28 | 估值对标 (Valuation) | 同赛道近期融资案例 PS/PE 倍数或管线折现值。 |
+| P29 | 退出路径 (Exit Strategy) | IPO 目标板块（科创板/18A 等）或潜在并购方名单。 |
+| P30 | 最终投资建议 (Recommendation) | 明确"拟投/不投/观察"建议及下一步 CDD 重点。 |
+
+### Slide 数量映射
+
+用户请求的 slide 数量不一定是 30 页。按以下原则分配：
+
+| 请求页数 | 分配策略 |
+|----------|----------|
+| ≤ 8 页 | 每阶段 1-2 页，聚焦执行摘要 + 核心科学 + 投资建议 |
+| 10-15 页 | 五阶段各取重点，跳过非核心子页 |
+| 20-30 页 | 完整五阶段，逐页展开 |
+| > 30 页 | 允许拆分子页（如 Benchmarking 按指标拆成多页） |
+
+## 2.5 调研指导 (Research Guidance for Deeptech)
+
+调研流程（文档扫描、提取、AI 补充、联网搜索、差距分析）的通用步骤和工具用法
+由 SKILL.md Phase 1.8 统一定义。**请严格遵循 SKILL.md 的调研协议。**
+
+本节只提供硬科技投研场景的**行业特定指导**，补充 SKILL.md 的通用流程。
+
+### 信息映射（SKILL.md Phase 1.8 Layer 1 提取后执行）
+
+将提取到的信息与报告结构框架（第 2 节）进行映射：
+
+| 信息来源 | 可能匹配的报告章节 |
+|----------|---------------------|
+| 论文 / 专利 PDF | P4-P5 第一性原理、P8-P10 专利与 IP、P11-P13 性能对标 |
+| 公司 BP / PPT | P1 执行摘要、P2 投资亮点、P26 股权结构、P27 融资方案 |
+| 财务数据 Excel / CSV | P28 估值对标、P29 退出路径 |
+| 访谈纪要 / 会议记录 | P3 关键风险、矛盾点监控 |
+| 行业研究报告 | P22-P25 行业拐点、市场规模 |
+| 产品测试数据 | P14-P18 数据验证 |
+| 团队简历 / 学术简历 | P6-P7 学术谱系 |
+
+### 联网搜索关键词策略（SKILL.md Phase 1.8 Layer 2.5 执行时参考）
+
+| 搜索目标 | 关键词策略示例 | 对应报告章节 |
+|----------|--------------|-------------|
+| 最新融资/估值 | `"[公司名] 融资 2024"`, `"[公司名] funding round"` | P28 估值对标 |
+| 竞品动态 | `"[技术领域] 竞争格局"`, `"[技术名] market landscape"` | P11-P13 性能对标 |
+| 市场规模 | `"[行业] 市场规模 预测"`, `"[industry] TAM SAM SOM"` | P22-P25 行业拐点 |
+| 专利动态 | `"[公司名] 专利 公告"`, `"[公司名] patent filing"` | P8-P10 专利与 IP |
+| 政策法规 | `"[行业] 政策 补贴"`, `"[行业] regulation update"` | P22-P25 行业拐点 |
+| 学术进展 | `"[技术名] Nature Science 2024"`, `"[技术名] breakthrough"` | P4-P5 第一性原理 |
+
+### 行业特定规则
+
+- 文档中的数据与 AI 知识 / 搜索结果冲突时，**以文档为准**
+- 文档中不同来源的数据冲突时，在风险页标注（见 §3 矛盾点监控）
+
+## 3. AI 逻辑引擎指令
+
+### TRL 自适应权重
+
+- 若 TRL < 4（基础研究 / 实验室验证阶段）：自动调高"学术谱系"及"第一性原理"权重至 60%，弱化"工程化量产"和"成本对标"
+- 若 TRL ≥ 4 且 < 7（中试 / 小批量阶段）：均衡分配
+- 若 TRL ≥ 7（量产就绪）：加重"工程化量产"及"成本对标"权重，弱化学术背景
+
+### 矛盾点监控
+
+实时核对不同来源的数据一致性：
+- "会议纪要"中提到的实验参数与"BP/论文"是否一致
+- 不一致处**必须在风险页标红**，附注"数据来源冲突：[Source A] vs [Source B]"
+
+### 标题结论化
+
+所有页面标题必须是结论性陈述，不能是描述性标题。
+
+| 正确 | 错误 |
+|------|------|
+| "技术领先同类竞品一个量级" | "技术介绍" |
+| "核心专利 5 年内无到期风险" | "专利分析" |
+| "创始人师承 Nature 通讯作者，学术壁垒显著" | "团队背景" |
+
+### 证据溯源
+
+关键数据必须标注来源：
+- `[Source: XX 论文 P12]`
+- `[Source: 创始人访谈记录 2024.03.15]`
+- `[Source: 招股书 P45]`
+- `[Source: 内部测试数据]`
+
+禁止出现无来源的关键数据断言。
+
+### 信噪比规则
+
+**严禁**出现以下无数据支撑的形容词：
+- "领先"、"卓越"、"顶级"、"世界一流"、"颠覆性"
+
+所有定性判断必须附带定量依据。如需表达领先性，用具体指标：
+- 正确："转化效率 23.5%，高于行业均值 19.2%（+4.3pp）"
+- 错误："转化效率行业领先"
+
+## 4. 视觉偏好（建议，可被 Design 覆盖）
+
+以下为该行业推荐的视觉风格。如果当前 active Design 有自己的定义，
+Design 的视觉规则优先。
+
+- **风格基调：** 深色科技感，强调精确性与数据密度
+- **图表交互：** 关键图表支持悬浮显示底层计算公式或实验原始片段
+- **数据呈现：** 优先使用 Stat Card + 对比表格，减少纯文字叙述
+- **颜色暗示：** 风险页使用红色强调色，机会页使用绿色/蓝色强调色

package/domains/general/INDUSTRY.md

@@ -0,0 +1,6 @@
+---
+name: general
+description: General purpose — no industry-specific structure or terminology
+author: slides-it
+version: 1.0.0
+---

package/index.ts

@@ -0,0 +1 @@
+export { default } from "./plugin.ts"

package/lib/agents/research-prompt.ts

@@ -0,0 +1,129 @@
+/**
+ * Revela Research Agent — system prompt
+ *
+ * Injected via plugin config hook into the `revela-research` subagent.
+ * The RESEARCH_AGENT_SIGNATURE is used by the system.transform hook to
+ * detect this agent and skip injecting the SKILL+DESIGN presentation prompt.
+ */
+
+export const RESEARCH_AGENT_SIGNATURE = "[[REVELA-RESEARCH-AGENT]]"
+
+export const RESEARCH_PROMPT = `${RESEARCH_AGENT_SIGNATURE}
+
+# Revela Research Agent
+
+You are a specialized research agent for Revela, an AI presentation generator.
+Your sole job is to **search, collect, and organize raw materials** for one research
+axis of a consulting or business presentation. You do NOT generate slides.
+
+You are launched in parallel with other research agents — each covering a different axis.
+Write your findings to a single file and return a brief summary.
+
+---
+
+## Your Mission
+
+Given a research brief specifying your topic and axis, you will:
+
+1. Scan the workspace for existing documents (always first)
+2. Search the web for current data, reports, and case studies
+3. Write all findings to ONE structured file: \`researches/{topic-slug}/{axis-name}.md\`
+4. Return a brief summary of what you found
+
+---
+
+## Step 1 — Workspace documents (always first)
+
+Use the **\`revela-workspace-scan\`** tool in a single call to discover all document
+files in the workspace (PDF, Word, Excel, PowerPoint, CSV, text).
+
+Then read every relevant file using the \`read\` tool. For PDFs and Office formats,
+the Revela plugin extracts text transparently — just call \`read\` normally.
+
+---
+
+## Step 2 — Web search (targeted)
+
+Formulate **3–6 targeted search queries** for your specific axis, covering:
+- Quantitative data (market size, growth rates, rankings, financials)
+- Source reports and analyst research
+- Company profiles and case studies relevant to your axis
+- Recent news, funding, or regulatory changes
+- Company logos, product screenshots, key personnel portraits (when profiling companies)
+
+For Chinese topics: search in **both Chinese and English**.
+
+Use \`webfetch\` to retrieve specific pages for depth. Do NOT use \`websearch\` —
+it is not available. Use \`webfetch\` with targeted URLs from your knowledge or
+from initial search results.
+
+---
+
+## Step 3 — Write findings file
+
+Use **\`revela-research-save\`** to write ONE file with all your findings.
+
+- \`topic\`: kebab-case slug shared across all agents for this presentation
+- \`filename\`: your axis name (e.g. \`market-data\`, \`catl-profile\`, \`tech-trends\`)
+- \`content\`: structured findings using the four sections below
+- \`sources\`: list of all URLs and filenames used
+
+### Findings file format
+
+Use these four sections — omit any that are empty:
+
+\`\`\`markdown
+## Data
+- {stat or finding} [Source: {url or filename}]
+- {stat or finding} [Source: {url or filename}]
+(5–10 items, most argument-worthy only)
+
+## Cases
+- **{Company/Entity}**: {1–2 sentence profile with key metrics} [Source: {url}]
+(2–4 entries max)
+
+## Images
+- {Description}: {url} | Alt: {brief alt text} | Use: logo|screenshot|portrait
+(only if found — do NOT fabricate URLs)
+
+## Gaps
+- {topic or data point not found or insufficiently covered}
+\`\`\`
+
+Content rules:
+- Every data point MUST have inline source attribution: \`[Source: {url}]\` or \`[Source: AI knowledge — verify]\` or \`[Source: {filename}]\`
+- Preserve raw numbers and direct quotes — do not summarize prematurely
+- Use tables for comparative data when 3+ entities are compared
+- Include publication dates where available
+
+---
+
+## Completion
+
+After writing the file, return this summary (do NOT include the raw data):
+
+\`\`\`
+Research complete: {axis-name} → researches/{topic-slug}/{axis-name}.md
+
+Key findings (3–5, most argument-worthy only):
+- {1–2 sentence highlight with source}
+- {1–2 sentence highlight with source}
+
+Gaps:
+- {any significant gaps}
+\`\`\`
+
+---
+
+## Rules
+
+- **NEVER** generate slide content or HTML — that is the primary agent's job
+- **NEVER** ask the user for information you can find through search or workspace files
+- **NEVER** use the raw \`write\` tool — always use \`revela-research-save\`
+- **NEVER** fabricate image URLs — only record URLs you actually found
+- **Always** include source attribution on every data point
+- **Always** use tables for comparative data (more useful than bullets for presentations)
+- **Preserve** raw data — the primary agent will select what to include in slides
+- **Note** data freshness — include publication dates where available
+- **One file only** — call \`revela-research-save\` exactly once with all your findings
+`

package/lib/commands/designs.ts

@@ -0,0 +1,59 @@
+/**
+ * lib/commands/designs.ts
+ *
+ * Handlers for design-related sub-commands:
+ *   /revela designs             — list installed designs
+ *   /revela designs <name>      — activate a design
+ *   /revela designs-add <url>   — install a design from URL / github:user/repo / local path
+ */
+
+import { listDesigns, activeDesign, activateDesign, installDesign } from "../design/designs"
+import { buildPrompt } from "../prompt-builder"
+
+export async function handleDesignsList(
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  const designs = listDesigns()
+  const current = activeDesign()
+  if (!designs.length) {
+    await send(`No designs installed. Use \`/revela designs-add <url>\` to install one.`)
+    return
+  }
+  const lines = designs.map((d) => {
+    if (d.name === current) {
+      return `🟠 **${d.name}**  —  ${d.description || "(no description)"}`
+    }
+    return `　 ${d.name}  —  ${d.description || "(no description)"}`
+  })
+  await send(`**Installed designs:**\n\n${lines.join("\n")}`)
+}
+
+export async function handleDesignsActivate(
+  name: string,
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  try {
+    activateDesign(name)
+    buildPrompt()
+    await send(`**Design activated:** \`${name}\`\nPrompt rebuilt. The new visual style will apply to the next message.`)
+  } catch (e: any) {
+    await send(`**Error:** ${e.message}`)
+  }
+}
+
+export async function handleDesignsAdd(
+  source: string,
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  if (!source) {
+    await send(`**Usage:** \`/revela designs-add <url|github:user/repo|local-path>\``)
+    return
+  }
+  try {
+    await send(`Installing design from \`${source}\`…`)
+    const name = await installDesign(source)
+    await send(`**Design installed:** \`${name}\`\nUse \`/revela designs ${name}\` to activate it.`)
+  } catch (e: any) {
+    await send(`**Install failed:** ${e.message}`)
+  }
+}

package/lib/commands/disable.ts

@@ -0,0 +1,14 @@
+/**
+ * lib/commands/disable.ts
+ *
+ * Handler for `/revela disable` — deactivates slide generation mode.
+ */
+
+import { ctx } from "../ctx"
+
+export async function handleDisable(
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  ctx.enabled = false
+  await send(`**Revela disabled.** Slide generation mode is off.`)
+}

package/lib/commands/domains.ts

@@ -0,0 +1,59 @@
+/**
+ * lib/commands/domains.ts
+ *
+ * Handlers for domain-related sub-commands:
+ *   /revela domains             — list installed domains
+ *   /revela domains <name>      — activate a domain
+ *   /revela domains-add <url>   — install a domain from URL / github:user/repo / local path
+ */
+
+import { listDomains, activeDomain, activateDomain, installDomain } from "../domain/domains"
+import { buildPrompt } from "../prompt-builder"
+
+export async function handleDomainsList(
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  const domains = listDomains()
+  const current = activeDomain()
+  if (!domains.length) {
+    await send(`No domains installed. Use \`/revela domains-add <url>\` to install one.`)
+    return
+  }
+  const lines = domains.map((d) => {
+    if (d.name === current) {
+      return `🟠 **${d.name}**  —  ${d.description || "(no description)"}`
+    }
+    return `　 ${d.name}  —  ${d.description || "(no description)"}`
+  })
+  await send(`**Installed domains:**\n\n${lines.join("\n")}`)
+}
+
+export async function handleDomainsActivate(
+  name: string,
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  try {
+    activateDomain(name)
+    buildPrompt()
+    await send(`**Domain activated:** \`${name}\`\nPrompt rebuilt. The new domain context will apply to the next message.`)
+  } catch (e: any) {
+    await send(`**Error:** ${e.message}`)
+  }
+}
+
+export async function handleDomainsAdd(
+  source: string,
+  send: (text: string) => Promise<void>,
+): Promise<void> {
+  if (!source) {
+    await send(`**Usage:** \`/revela domains-add <url|github:user/repo|local-path>\``)
+    return
+  }
+  try {
+    await send(`Installing domain from \`${source}\`…`)
+    const name = await installDomain(source)
+    await send(`**Domain installed:** \`${name}\`\nUse \`/revela domains ${name}\` to activate it.`)
+  } catch (e: any) {
+    await send(`**Install failed:** ${e.message}`)
+  }
+}