{"type":"rich","version":"1.0","title":"BrettPhillips wrote","author_name":"BrettPhillips (npub1rv…af8df)","author_url":"https://nostr.now/npub1rvqzg0lsgsnnmrjxelt44vml99gul28mverm80ht4wad5cjmdesqqaf8df","provider_name":"njump","provider_url":"https://nostr.now","html":"Everywhere I can. \nLet’s say I need to build a feature, take for instance a common task of integrating with Stripe. \nI’ll start by gathering a few links to api documentation and use the Claude chat to say something along the lines of “research integrating with Stripe for invoicing referencing this links. Create a detailed design spec for the features”\nThen I’ll take that spec, give it a once over and save it to my code workspace. \nI’ll execute Claude Code and prompt something like “Think about the design spec for integrating stripe and create a detailed implementation plan to integrate Stripe in this application staying true to the projects conventions”. \nI’ll give that a once over and maybe even ask it to validate the plan against the original spec. \nOnce I’m satisfied with the spec I say “execute the plan”. \nI then move to a different project while it’s running and repeat back and forth. \nI’ve been very happy with the quality of code given enough context and guidelines. "}