Slop guide, using Claude projects. You have to chunk the codebase into pieces small enough for Claude to digest, about 40,000 tokens per file, using something like code2prompt. I have a lot of repos catalogued: Applesauce, Quartz (pre-outbox), Amber, go-nostr, nostr-tools, Welshman, NAK, Bostr2, Citrine, HAVEN, Nostream, Strfry, Jumble, Grain, and Wisp. ## Querying a Codebase **FILL IN: CONCEPT** Initial Prompt: ``` Look up how this project handles CONCEPT. ``` Followup: ``` write up a design specification for how this project handles CONCEPT, with implementation details and code snippets. Be very detailed. ``` Capture this in a document, labeled with the project it specifies. ## Building the Specification After collecting all the documents, add it as context to a prompt alongside the Core Protocol Spec and any others whose style you want to emulate. Chat flow: **FILL IN: CONCEPT** ``` Here are design specifications for how various nostr projects handle CONCEPT. I want you to write up a protocol specification for how this document is handled following the style of the references, "Nostr Protocol Specification", and "Nostr Client-Relay Transport Specification" This document should be language agnostic and never mention NIPs. It should be split up based on what all of the implementations agree on vs what is optional. First task: find all the rules that are common to each implementation and all the rules that are implementation specific. ``` Rules were listed out. Many implementation specific items were unrelated to the protocol and just specific platform or language details. These had to be removed. **FILL IN: CONCEPT** ``` For the implementation specific details, filter out those that are more related to language or platform details vs the protocol level of CONCEPT. Then group the remaining according to topic or theme. ``` Get the implementation specific protocol rules. **FILL IN: DOCUMENT_NAME** ``` Write up the final "Nostr DOCUMENT_NAME Specification" document, following the style of the provided references. ``` Get the final spec.

useful slop, sounds progressive

Very useful slop, yes.

👀

usefulest slopest

I like that there are so many implementations on Nostr. Because I can rip the de-facto standards out of the code rather than read nips.