Guides
How to make ProjectShelf match the machine you actually work on, and how people use it for work that is not source code.
Setup
Setting up ProjectShelf on Windows
Get the most out of the built-in presets: Windows Terminal profiles, PowerShell against Command Prompt, Git Bash path formats, and why Command Prompt needs a different directory change prefix.
Setting up ProjectShelf on macOS
Replace the Windows presets with Terminal, iTerm2, Warp, and Finder, and add the editor command line tools so ProjectShelf generates commands that work on a Mac.
Setting up ProjectShelf on Linux
Configure GNOME Terminal, Konsole, Alacritty, or your shell of choice, wire up xdg-open for file managers, and replace the Windows presets with commands that work on your distribution.
Configuration
Writing command templates
Every placeholder ProjectShelf substitutes, how templates attach to a tool, and worked examples for development servers, git operations, and multi-line workflows.
Rebinding keyboard shortcuts
Record any key combination against any action, understand shortcut scopes, resolve conflicts, and reach every command from the palette when no key is bound.
Workflows
Launch sets: opening a whole context at once
Group the projects you work on together, generate the commands for all of them in one action, and build sets around a client, a service, or a time of day.
ProjectShelf for designers: Figma, Canva, and local design files
Keep Figma files, Canva designs, asset folders, and client work in one searchable place, and open the right file in the right application without hunting through tabs.
ProjectShelf for researchers and writers
Track papers, datasets, and long documents alongside the tools that open them, from Obsidian vaults and LaTeX projects to Zotero libraries and reference folders.
Your data
Nothing here needs reading first. The application works out of the box and these are for when you want it to fit your setup exactly.
Open ProjectShelf