New guide: turn a new Mac into an agent-native dev machine, and Michael's prompt now comes in Starship too
Our setup guides assumed a Mac that already had Apple's developer tools, Homebrew, and a terminal someone had opened before. The new guide starts from a Mac out of the box and goes in nine steps to Claude Code, GitHub, short machine names, Lossless agent skills, and Context Vigilance. The terminal guide gains a Starship version of the my-tokyo prompt, so a machine set up with either engine looks the same.
A new Mac, ready for agents
[[guides/agent-native-dev-machine/index|A Few Easy Steps to Turn Your Mac into an Agent-Native Dev Machine]] came out of setting up someone’s brand-new Mac in real time. Each step is one we actually hit along the way.
- Before you start: how to open Terminal, for readers who haven’t since a college course.
- 1. Xcode, plus the lighter Command Line Tools option.
- 2. Homebrew, with what a package manager is and the “Next steps” lines people skip.
- 3. Claude Code, early, so it can do the rest of the steps for you.
- 4. The GitHub CLI, with git’s name and email set from your GitHub account.
- 5. Short names, like
mps@m4, so the prompt stays readable and shows who did the work and on which machine. - 6. A
~/codefolder for every project. - 7. Lossless agent skills, the ones useful to anyone doing development work.
- 8. Terminal setup (optional), pointing to the Ghostty guide.
- 9. Context Vigilance, with the kit’s one-command install marked as coming soon.
The same prompt, in Starship
[[guides/terminal-setup-ghostty-oh-my-posh/index|Getting Unafraid and Setting Up Your Terminal]] now has a Starship port of the my-tokyo prompt alongside the Oh My Posh original. It has the same frame, colors, and segments, and it was tested by rendering it with starship prompt. The few places where the two engines differ are listed in the guide.