> For the complete documentation index, see [llms.txt](https://www.macsetup.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.macsetup.xyz/master.md). # Introduction A Product Designer’s Guide to Setting Up a Machine for Designers Updated for macOS Tahoe This guide started as a way to create a designer-friendly, vibe-coded development environment based on my experience at [GoDaddy](http://godaddy.com/). It evolved from a UI development setup used by designers at [Symph](https://www.symph.co/) and [Abstract Digital](https://abstract.ph/). Now, I’m sharing it to help design teams—and anyone who loves shipping digital products—move faster. 🚀 If you: * Want a consistent development environment for your design team ⚡ * Are a designer looking for simple, step-by-step instructions to set up dev tools 💻 * Want a terminal setup that looks as good as it works 💪 Then this guide might be for you. Feel free to use, share, or fork this guide. You don’t need to follow it exactly—it reflects my personal workflow and tech stack, so adapt it to fit your needs. 🦄✨ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.macsetup.xyz/master.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.