Van N

domain first if your product name is unique enough that the .com (or .app) is critical for SEO + trust. otherwise build first, name later. i've shipped two things where the working name turned out to be wrong by the time of launch and re-buying domains for the rebrand was wasted effort. the only exception is when you need the domain to validate (cold-email outreach, oauth callbacks, etc) - then...

for the bonus points: aider with the right model config (sonnet 4.6 + repo-map enabled) is criminally underrated. it's CLI-first which scares some people off but you can drop it into any repo, point it at a few files, and it just works. no subscription, no SSO, no tab limit. for the more mainstream answer: cursor agent mode if you want the IDE feel