Workflows

Last updated: 2026-08-05

Overview

Different ways to use Dev WorkDir, depending on how you work. Pick the workflow that fits you — or mix and match.

Workflow 1: The Vibe Coder

You have lots of side projects and jump between them constantly.

Setup

  • Add all your side project folders
  • Set your default AI editor (Cursor / Windsurf / Trae)
  • Set up double-click actions for each project

Daily Flow

  1. Get an idea → menu bar → Create Project → 30 seconds later you’re coding
  2. Working on Project A, get an idea for Project B → add a todo to Project B → back to A
  3. Want to switch → menu bar → click → open
  4. End of day → close everything → all projects safe in Dev WorkDir

Why It Works

  • Zero friction to start new things
  • Never lose an idea
  • Fastest possible project switching

Workflow 2: The Indie Hacker

You’re building a product (or products) and need to stay organized.

Setup

  • One directory per product
  • Project todos for feature ideas and bugs
  • Environment variables configured per project
  • Monorepo support if needed

Weekly Flow

  1. Monday: Review todos across all projects, plan the week
  2. Focus on one project at a time (deep work mode)
  3. Use menu bar for quick checks, main window for deep management
  4. Friday: Wrap up, update todos, plan next week

Why It Works

  • Everything in one place
  • No more “what was I doing on that project?”
  • Todos stay with the project, always

Workflow 3: The Monorepo Developer

You work in a monorepo with multiple packages and apps.

Setup

  • Add your monorepo root
  • Dev WorkDir auto-detects sub-projects
  • Configure favorite editors per sub-project type

Daily Flow

  1. Open monorepo → see all sub-projects
  2. Jump into the one you’re working on
  3. Need to check another? 2 clicks
  4. Create new sub-projects in seconds

Why It Works

  • No more navigating deep directory structures
  • Every sub-project is one click away
  • New packages created in the right place automatically

Workflow 4: The Learner

You’re learning new tech and have lots of tutorial/experiment projects.

Setup

  • Create a “learning” directory
  • Create projects from templates as you follow tutorials
  • Add todos with notes and questions

Learning Flow

  1. Start a new tutorial → create project from template
  2. Follow along, experiment freely
  3. Add todos: “come back to this”, “try this variation”
  4. Later, review and pick up where you left off

Why It Works

  • Each tutorial is its own clean project
  • Notes are tied to the project
  • Easy to come back to old experiments

Workflow 5: The Multi-Editor Dev

You use different editors for different things.

Setup

  • Dev WorkDir auto-detects all your editors
  • Set default per project type
  • Or just use “Open With” whenever

Typical Setup

  • VS Code — web projects
  • Cursor — AI-assisted coding
  • Xcode — iOS/Swift projects
  • Claude Code — when you want CLI AI coding

Daily Flow

  • Open web project → VS Code or Cursor
  • Open Swift project → Xcode
  • Want AI help → right-click → open in AI editor
  • All from Dev WorkDir

Build Your Own Workflow

These are just starting points. The best workflow is the one that fits how you work.

Experiment with:

  • Different directory structures
  • Different editor setups
  • Different ways of using todos
  • Menu bar vs main window usage

Find what works for you, and run with it.

Work the way you want. Dev WorkDir adapts to you.