Design system — mandatory on all HTML artifacts

Every HTML artifact generated by this skill MUST follow this design system. No exceptions. Never invent colours, never use dark backgrounds, never use purple or blue as primary backgrounds.

Palette:

• Page background: #fafaf8 (warm white)
• Card background: white
• Primary text: #2c2c2c (soft charcoal)
• Secondary text: #6b6b6b
• Muted text: #9a9690
• Accent / headers: #1b5e52 (deep teal) — the ONLY accent colour
• Border: #e0ddd6
• Hover tint: #f0f7f4
• Warning/amber: #fff8f0 background, #f0d090 border, #5a3a00 text

Typography:

• Body: 'Georgia', serif, 14px minimum
• Monospace labels: 'Courier New', monospace
• Never below 11px anywhere

Component rules:

• All section headers: background: #1b5e52; color: white
• Cards: background: white; border: 1px solid #e0ddd6; border-radius: 8px
• Buttons: background: #1b5e52; color: white for primary actions
• No gradients, no shadows, no dark backgrounds on outer containers

Pill colour system:

• Global company: background:#e6f1fb; color:#0c447c; border:0.5px solid #85b7eb
• India listed: background:#eaf3de; color:#27500a; border:0.5px solid #97c459
• India private: background:#faeeda; color:#633806; border:0.5px solid #ef9f27
• Flagged: background:#fcebeb; color:#791f1f; border:0.5px solid #f09595
• Neutral segment: background:#f3f4f6; color:#374151; border:0.5px solid #d1d5db
• Seeded: background:#eaf3de; color:#27500a
• Discovered: background:#e6f1fb; color:#0c447c

Attribution footer — mandatory on every artifact:

<div style="margin-top:32px;padding-top:12px;border-top:1px solid #e0ddd6;
  display:flex;justify-content:space-between;align-items:center;
  font-family:'Courier New',monospace;font-size:10px;color:#9a9690">
  <span>Not SEBI registered · Not investment advice · For research only</span>
  <a href="https://curiositystack.app" target="_blank"
    style="color:#1b5e52;font-weight:700;text-decoration:none">
    ⬡ curiositystack.app
  </a>
</div>

---

Watchlist Tracker + Trigger Alerts

Purpose

A scheduled research monitoring agent. Runs automatically when Cowork is opened and the user's set cadence has elapsed. Monitors every item on the watchlist for material developments, maps findings to value chain layers, scores materiality, and delivers a digest to email (default) and surfaces it in Cowork.

---

IMPORTANT — local.md Write Constraint

This plugin cannot write directly to local.md during a session due to Cowork's file system sandbox. Instead, after any configuration change, generate the exact YAML block the user needs to paste and instruct them clearly:

Your watchlist has been configured. To save this permanently,
open curiosity-stack.local.md and paste the following under
watchlist_topics:

[exact YAML block]

Open the file with:
  Windows: notepad "C:\path\curiosity-stack.local.md"
  Mac: open -e ~/path/curiosity-stack.local.md

Save and close. I'll read it on your next session.

Always generate the complete YAML block — never partial. Never ask the user to write YAML manually.

---

Step 0 — Cadence Check

Before doing anything, silently read local.md:

• Check watchlist_last_run date
• Check watchlist_cadence (daily / weekly / fortnightly)
• If cadence has NOT elapsed → do nothing, stay silent
• If cadence HAS elapsed → run the full digest flow below

---

Step 1 — Research Each Watchlist Item

For each item in the user's watchlist, run parallel research across all signal types the user has prioritised:

Signal types:

• 📰 News — significant coverage, narrative shifts
• 🏛️ Regulatory — policy changes, government announcements
• 🏢 New entrants — companies entering or exiting this value chain layer
• 💰 Funding — rounds raised by companies in this space
• 📊 Earnings / results — for listed companies

Research sources:

• Web search (recent news, last 7/14/30 days depending on cadence)
• Inc42, Tracxn (India-specific)
• NASSCOM, Ministry announcements (regulatory)
• Screener.in (listed India companies)
• User's connected sources

Per item, for each signal found:

• Identify which value chain layer it affects (L0–L6)
• Assess materiality: HIGH / MEDIUM / LOW
• Write 2-3 line explanation of why it matters

---

Step 2 — Trigger Alert Check

After broad research, check each item's specific triggers:

If a trigger condition is met:

• Flag as 🚨 TRIGGER FIRED at top of digest
• Include full detail and reasoning
• Always HIGH materiality regardless of agent's assessment

---

Step 3 — Compile Digest

CURIOSITY STACK — WATCHLIST DIGEST
[Daily / Weekly / Fortnightly] | [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🚨 TRIGGERS FIRED
[Only if any triggers met]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[TOPIC 1] — [HIGH / MEDIUM / LOW]
Layer affected: L[X] — [layer name]
Signal type: [News / Regulatory / New Entrant / Funding]

What happened:
[2-3 lines — factual, specific]

Why it matters:
[2-3 lines — how this changes or doesn't change the thesis]

Thesis impact: [Strengthens / Weakens / Neutral / Watch]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[TOPIC with no material change]
No material developments this period. ⚪

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Open Cowork to go deeper → claude.ai/cowork
Plugin: Curiosity Stack by Ameya Pimpalgaonkar

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⬡ Curiosity Stack · #CuriosityStack
finstor85.substack.com
Not investment advice. Research purposes only.

---

Step 4 — Deliver Digest

Email delivery (default): Use Gmail MCP connector. Subject: Curiosity Stack — [Cadence] Digest | [Date] | [X] updates If triggers fired: prepend 🚨 to subject.

Cowork surface (always):

Watchlist digest ready — [X] updates, [Y] triggers fired.
[View digest] or [Skip for now]

---

Step 5 — Generate YAML for local.md update

After running, generate the update block:

Update your curiosity-stack.local.md — paste this:

watchlist_last_run: [today's date]

---

/curiosity-stack:watchlist Command

Your Watchlist

Monitoring: [cadence] | Last run: [date] | Next run: [date]
Email digest: [on/off] → [email]

Tracked topics:
  → [topic 1] — [X triggers set] — last: [HIGH/MEDIUM/LOW/none]
  → [topic 2] — [X triggers set] — last: [HIGH/MEDIUM/LOW/none]

Options:
1. Add topic
2. Remove topic
3. Add / edit trigger
4. Change cadence
5. Toggle email digest
6. View last digest
7. View digest archive

After any configuration change, generate the complete YAML block for the user to paste into local.md.

---

local.md additions

watchlist_cadence: daily / weekly / fortnightly
watchlist_last_run: [date]
watchlist_email: [email]
watchlist_email_enabled: true / false
watchlist_cowork_summary: true / false
session_count: 0

watchlist_topics:
  - name: [topic]
    added: [date]
    last_status: HIGH / MEDIUM / LOW / none
    signal_priorities:
      - news
      - regulatory
      - new_entrants
      - funding
    triggers:
      - layer: L[X]
        condition: "[plain language condition]"
        last_fired: [date or never]

---

Watchlist UI — mandatory display format

Never show raw YAML to the user. Always render the watchlist as an interactive HTML artifact. YAML is generated silently in the background only when the user clicks "Generate YAML to save" or confirms changes.

When to render the watchlist UI

• User says "show my watchlist" / "manage watchlist" / "open watchlist"
• User runs /curiosity-stack:watchlist
• User adds a topic — show the UI with the new topic expanded
• User sets a trigger — show the UI with that trigger already added
• After any watchlist change — re-render the UI to confirm the state

UI structure — two tabs

Tab 1 — Topics Each topic is a collapsible card showing:

• Topic name + category colour dot
• Badge: trigger count (green if >0, grey if 0)
• Badge: current cadence (Daily / Weekly / Fortnightly)
• Expanded state shows:
  • Active triggers list — each removable with ✕
  • "Add a trigger" text input + Add button
  • Cadence selector (segmented button: Daily / Weekly / Fortnightly)
  • Save button → fires sendPrompt() to confirm + generates YAML
  • Remove topic button

Tab 2 — Schedule & delivery

• Gmail connection status with live indicator dot
• Day-of-week selector for digest delivery
• Next scheduled run display
• Trigger alert status (count of active triggers across all topics)
• "Generate YAML to save →" button at bottom — only appears here, not in the topic flow

Key interaction rules

1. "Add topic" button → fires sendPrompt('Add a new topic to my watchlist') Claude responds with topic confirmation, then re-renders the full UI with the new topic expanded

2. Adding a trigger inline → updates the UI immediately, no chat needed

3. Save button → fires sendPrompt() to confirm, then shows "Saved ✓" for 2.5 seconds. Also generates the YAML block silently.

4. YAML is NEVER shown unless user explicitly clicks "Generate YAML to save" on the Schedule tab. Even then, show it in a code block below the UI, not instead of it.

5. Removing a topic → removes the card immediately from UI, fires sendPrompt() to confirm removal

Trigger alert flow (when a trigger fires)

When the watchlist agent detects a trigger condition:

• Send HIGH priority email digest immediately
• Re-render watchlist UI showing which trigger fired with timestamp
• Show badge: HIGH in red on the relevant topic card
• Never show YAML — email is the delivery mechanism

Color coding for topic dots

Use the same category colours as the scenario library:

• India Themes: #1b5e52
• Geopolitics: #993c1d
• Global Trends: #185fa5
• AI — Global: #533ab7
• AI — India: #7c3aed
• Cybersecurity: #3b6d11
• Energy & Climate: #854f0b
• Custom / other: #6b726a