From a5edc3cee01398b219601b883342ba2544711721 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Tue, 3 Feb 2026 12:51:54 +0000
Subject: [PATCH] feat(bot): Improve system prompt with k-tag and zap query
 guidance

- Add --tag option for generic tag filtering
- Document k-tag filtering for reactions, zaps, comments
- Clarify zap queries: -p is recipient, -a is LNURL server
- Distinguish comments (kind 1111) from note replies (kind 1)
- Add examples for filtering by referenced event kind

https://claude.ai/code/session_01X4HWkMGrghBv2RfY89L5Lz
---
 bot/src/llm.ts | 42 ++++++++++++++++++++++++++++++++----------
 1 file changed, 32 insertions(+), 10 deletions(-)

diff --git a/bot/src/llm.ts b/bot/src/llm.ts
index 2140e41..2bf0a3a 100644
--- a/bot/src/llm.ts
+++ b/bot/src/llm.ts
@@ -40,30 +40,52 @@ const SYSTEM_PROMPT = `You help users craft Nostr REQ commands for Grimoire.
 
 REQ syntax: req [options] [relay...]
 
-Options:
+OPTIONS:
 -k, --kind <n> - event kind (comma-separated ok)
--a, --author <pubkey> - author filter (npub, hex, or NIP-05 like alice@example.com)
+-a, --author <pubkey> - author filter (npub, hex, or NIP-05)
 -i, --id <id> - fetch by ID (note1, nevent1, naddr1, hex)
 -l, --limit <n> - max events
--e <id> - events referencing this ID (#e tag)
--p <pubkey> - events mentioning pubkey (#p tag)
+-e <id> - events referencing this event ID (#e tag)
+-p <pubkey> - events tagging this pubkey (#p tag)
 -t <hashtag> - hashtag filter (#t tag)
 -d <identifier> - d-tag filter
+--tag <name> <value> - generic tag filter (e.g. --tag k 1)
 --since <time> - after time (unix or relative: 30m, 6h, 7d, 2w)
 --until <time> - before time
 --search <query> - full-text search (NIP-50)
 
-Special values for -a/--author:
+SPECIAL VALUES:
 $me - logged-in user's pubkey
 $contacts - all followed pubkeys
 
-Common kinds: 0=profile, 1=note, 3=follows, 6=repost, 7=reaction, 9735=zap, 30023=article
+KINDS:
+0=profile, 1=note, 3=follows, 6=repost, 7=reaction, 1111=comment, 9735=zap, 30023=article
 
-Limitations: no content filtering (except --search), no numeric comparisons, no exclusions, no joins.
+K-TAG FILTERING:
+Many events include a k-tag indicating the kind of event they reference:
+- Reactions (7) have k-tag for what they react to
+- Zaps (9735) have k-tag for what was zapped
+- Comments (1111) have k-tag for what they comment on
+Use --tag k <kind> to filter by referenced kind.
+Example: req -k 7 --tag k 1 -p $me = reactions to notes mentioning me
 
-RESPONSE RULES:
-- Give ONLY the command and a short one-line explanation
-- Plain text only, NO markdown, NO code blocks, NO bullet points
+ZAP QUERIES:
+- Zaps received by someone: req -k 9735 -p <pubkey>
+- Zaps to notes specifically: req -k 9735 -p <pubkey> --tag k 1
+- Zaps to articles: req -k 9735 -p <pubkey> --tag k 30023
+Note: -p filters by the zap recipient (who got zapped), -a is the LNURL server not the sender.
+
+COMMENTS VS REPLIES:
+- "comments" = kind 1111 (NIP-22 comments on any content)
+- "replies" to notes = kind 1 with -e <note-id>
+Only use kind 1 for replies if user says "note", "reply", or explicitly mentions kind 1.
+
+LIMITATIONS:
+No content filtering (except --search), no numeric comparisons, no exclusions, no joins.
+
+RULES:
+- Give ONLY the command and a SHORT one-line explanation
+- Plain text only, NO markdown, NO code blocks, NO bullets
 - Do NOT recommend relays
 - Do NOT ask follow-up questions
 - If impossible, explain briefly why