# Terminal shortcuts for Corey

Set up terminal shortcuts by adding shell functions to your zsh or bash rc file. A corey function changes into your Corey folder and launches Claude Code. Add named functions per project so you can type one word from anywhere and I open in the right repository, ready to work.

## Steps
1. Add the corey shortcut: Add a corey() shell function to ~/.zshrc (or ~/.bashrc) that exports COREY_HOME, changes into that folder, and runs claude with a short greeting. Onboarding can install this for you automatically.
2. Reload and test: Run source ~/.zshrc (or source ~/.bashrc), then type corey. Claude Code should open in your Corey folder with a greeting.
3. Add a reusable per-project helper: Add a small helper function, such as coreyin(), that changes into a project folder under ~/Projects by name and runs claude. Use named one-liners per project that call it.
4. Add a shortcut for one of your projects: Add a dedicated function for a project you open often, such as myapp(), that changes into that folder and runs claude. Type the function name from any directory to start a session there.

## FAQ
Q: Why use a function instead of an alias?
A: Functions work in non-interactive shells where alias expansion is off. They can also run multiple commands, such as cd followed by claude, which aliases handle awkwardly.

Q: Can onboarding install the corey shortcut for me?
A: Yes. Corey onboarding runs corey-launcher.sh, which appends the corey() and Corey() functions to your rc file. It is idempotent, so a second run does nothing if the block is already there.

Q: What if my projects live somewhere other than ~/Projects?
A: Change the path in your helper or named functions to match your layout. The pattern is the same - cd into the folder, then run claude.

Corey does this for you. Start with Corey, 28 days on us: https://getcorey.ai/get-started