01Links
Claude Code
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
Speak the job, the look and the stack in one brief, so your agent gets the context together.
Why I keep it
I use Wispr Flow to talk to my agents because speaking gets the whole context out together: what I want, how it should look and the stack I’m using. I dictated briefs and feedback during this build, so the agent had more than a short request to work from.
It types into the app I’m using, so the conversation stays where the job is happening. I’ve linked the deal through Vouchernaut, my own site; use it to try dictating a full brief or the feedback you’d otherwise trim down while typing.
01Links
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
02Links
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
03Links
Keep separate jobs open across Claude accounts, with Notch showing which account has room to work.
04Links
Carry a visitor’s voice-agent answers into a call booking, so they don’t have to start again.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.