The documentation from the homebrew docs is sufficient to creating a new tap. I will add a bit of commentary in addition to the above to discuss the design choices I made when making my homebrew tap & cask for window-switcher.

First of all, I chose to create a repository on GitHub, since that is where my code is stored. Some bikeshedding - what should I name my tap?

Note: [GitHub Only] The brew.sh docs recommended adding a prefix to your homebrew tap repo with homebrew- if you want users to take advantage of the brew tap comamnd. However, when others install or tap from your repo, they do not include the prefix. For example, the repo github.com/sean01zhang/homebrew-formulae can be accessed by executing brew tap sean01zhang/formulae.

Since finishing my last internship, I’ve missed having massive monitors at work. No longer could I have two windows in split view without sacrificing content space.

This meant that I had many apps occupying one desktop at once. However, as a certified non-minimalist^TM, I have too many windows open. For example, I have multiple instances of Firefox open (one for each profile), multiple instances of Finder with different folders open, and if I wasn’t a vim user, I would have many different instances of my favourite GUI-based code editor open (one for each repository I was working on).