The Magic of “Cd Create”: Streamlining Your Command Line Workflow

If you spend any amount of time in a terminal—whether you’re spinning up a quick prototype, organizing a data science project, or managing a massive codebase—you’ve undoubtedly performed this ritual thousands of times:

mkdir my-new-project
cd my-new-project

It’s second nature. You create a directory, and immediately after, you change your working directory (cd) into it. But efficiency-minded developers have long asked: Why should this take two separate commands?

Enter the philosophy of “cd create”—the practice of combining directory creation and navigation into a single, seamless terminal action.

Why the Two-Step Dance Gets Old

Typing mkdir followed by cd isn’t physically difficult, but from a cognitive and typing perspective, it introduces unnecessary friction:

• Repetition: You are typing out the exact same directory name twice in a row.
• Context Switching: Even if it takes three seconds, breaking your workflow to issue two commands creates micro-interruptions in your flow state.
• Error Prone: If your directory name is long or complex (