Building Your Command Library
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 6 · Section 4 of 5
Building Your Command Library
Start with the workflows you already have. Look at what you’ve been typing repeatedly and turn each one into a command.
Good candidates for early commands:
/morning — your morning check-in. Review inbox, projects, calendar note. Tell me what to focus on.
/process-inbox — read each item in 01 Inbox, suggest where it belongs, and list items I need to action rather than file.
/weekly-review — run across the week’s daily notes, completed project updates, and any captures. Give me a summary of what happened and what’s carrying forward.
/capture — take what I’m about to type and create an inbox note with today’s date and the right metadata.
Each command you write encodes your judgment about what a good version of that workflow looks like. You’re not just automating a task — you’re capturing your best thinking about how to do that task.