<oembed><type>rich</type><version>1.0</version><title>BrettPhillips wrote</title><author_name>BrettPhillips (npub1rv…af8df)</author_name><author_url>https://nostr.now/npub1rvqzg0lsgsnnmrjxelt44vml99gul28mverm80ht4wad5cjmdesqqaf8df</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Everywhere I can. &#xA;Let’s say I need to build a feature, take for instance a common task of integrating with Stripe. &#xA;I’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”&#xA;Then I’ll take that spec, give it a once over and save it to my code workspace. &#xA;I’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”. &#xA;I’ll give that a once over and maybe even ask it to validate the plan against the original spec. &#xA;Once I’m satisfied with the spec I say “execute the plan”. &#xA;I then move to a different project while it’s running and repeat back and forth. &#xA;I’ve been very happy with the quality of code given enough context and guidelines. </html></oembed>