https://npub1yms0ptszca8sxwyewty9tfqkme0kk8ymglc8f42w68gncv8mdf4q87xdw2.nostrdeploy.com/
"Build a nostr calendar application called NostrCal. The application should resemble Calendly "
It completed for about $10 in credits. I'm interested to know if I had been able to get my full prompt in what it would have been like. Have you made any posts on how much you're spending per app that you've been building nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq37amnwvaz7tmwdaehgu3dwfjkccte9ejx2un9ddex7umn9ekk2tcqyqlhwrt96wnkf2w9edgr4cfruchvwkv26q6asdhz4qg08pm6w3djg3c8m4j?
Also do you have any suggestions for feeding it non-adopted NIPs? I'm guessing it's not been trained on things like NIP-100 or even new NIPs you may want to propose so curious what's the best way to feed that to it. Would it be best to just write out the NIP and leave it in the working folder and tell it to address it?
$10 for one prompt is about right.
I would copy and paste entire json string examples or entire NIP text into the promt to teach it about a new and proposed NIP. You can also post the naddr if it's a custom NIP like from nostrhub.io or you can create an MD file and paste the proposed NIP into that and tell Dork to read from custom-nip.md for example. As you know new line breaks don't work so if I'm using Dork I would create a file manually.
How much do you usually spend on post deploy edits? I'm sure that can be a wide variance based on how many files it needs to rewrite for the function it's building but in general have you noticed any post deploy cost per prompt avg?
Yes. It gets expensive. I've found it cheaper to switch to one feature per prompt when working on edits. But even then, I'd it's a massive project, the context will regrow quickly. Some of us have used Sonnet 4 for initial rollout and then switch to maybe Gemini Pro or Sonnet 3.7 for cheaper model usage for small changes. But beware, Claud Sonnet 4 by far does better jobs for larger and more complex changes.
