01Links
Codex
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
How I use it
I use Claude Code because it works inside the repo, where I keep the plan, skills, desks and checks. It reads the same files I do, so the instructions can stay with the work. Separate sessions each take a job in their own git worktree.
I keep the decisions; the agents do most of the typing. The tech-lead skill gives a build its routine, while /desk opens standing work from its saved records. Add the skills you need, so a new session starts with a method as well as a prompt.
01Links
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
02Links
Keep separate jobs open across Claude accounts, with Notch showing which account has room to work.
03Links
Speak the job, the look and the stack in one brief, so your agent gets the context together.
05Links
Give apps and tools their own shortcuts, so you can switch contexts from the keyboard.
06Links
Turn Caps Lock into all four modifiers, so new shortcuts don’t clash with app defaults.
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.