Feels kinda weird to pay Claude $12.11 to refactor code it wrote itself. 🤔

Talk to @jc4p he might have perspective here

the trick is to have Claude write PRDs and detailed attack plans first then ONLY follow those, otherwise you’ll be get stuck in circles often. example: https://gist.github.com/jc4p/4252061ac04720db80867f874ca64545 — all i do is open the IDE and say “it’s wednesday week 2, you’re the lead dev, go”

The Farcaster formerly known as Kchamp. Books, beats, bodybuilding, bright ideas and beautiful things.

katherinechampagne.com

def want to try this, but often find it’s ignores or misunderstand requirements, or ignores its own summaries of work done so far when picking back up. but the prds mine spits out are not nearly as comprehensive

what makes a good initial prd prompt? how much do you manually tweak before unleashing?

prev: /nook, protocol @ opensea, co-author seaport & stuff.
professional @slokh and @0xalexander fanboy

the most important part of the PRD when it comes to AI writing is the "Roles & Responsibilities" section and the weekly roadmap section, any time the AI missteps you can say "Remember, it's Week 1 and you are focused on Week 1's deliverables ONLY"

here's an example of a whole chat from initial concept to final PRD (it's for a mini app i want to make in the future for private anonymous chatrooms):

here's an example of a whole chat from initial concept to final PRD (it's for a mini app i want to make in the future for private anonymous chatrooms): https://claude.ai/share/63e295c5-5dbd-4d80-80df-9edf4a21f83a

excellent, i like that. will give it a shot soon 🫡 ty!