From cd5376ff492b9ccce38b2feef92476a95136cffd Mon Sep 17 00:00:00 2001 From: Alex Gleason Date: Sun, 15 Jun 2025 10:55:39 -0500 Subject: [PATCH] Add missing nostr__ server prefixes --- CONTEXT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTEXT.md b/CONTEXT.md index cb72d32..76710df 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -120,7 +120,7 @@ Knowing when to create a new kind versus reusing an existing kind requires caref When implementing features that could use existing NIPs, follow this decision framework: -1. **Thorough NIP Review**: Before considering a new kind, always perform a comprehensive review of existing NIPs and their associated kinds. Use the `nostr__read_nips_index` tool to get an overview, and then `read_nip` and `read_kind` to investigate any potentially relevant NIPs or kinds in detail. The goal is to find the closest existing solution. +1. **Thorough NIP Review**: Before considering a new kind, always perform a comprehensive review of existing NIPs and their associated kinds. Use the `nostr__read_nips_index` tool to get an overview, and then `nostr__read_nip` and `nostr__read_kind` to investigate any potentially relevant NIPs or kinds in detail. The goal is to find the closest existing solution. 2. **Prioritize Existing NIPs**: Always prefer extending or using existing NIPs over creating custom kinds, even if they require minor compromises in functionality.