🛠️ Your Personal Workflow

The first step to speeding up your workflow is to create aliases in your .bashrc or .zshrc. Claude Code is a command you’ll type dozens of times a day. Shortening claude to cc already saves 4 characters per use.

Beyond the basic alias, create aliases for compound operations you repeat often: resume the last session, run in one-shot mode with a specific model, or start in a specific folder.

# Aliases para Claude Code
alias cc='claude'
alias ccr='claude --resume'
alias ccp='claude -p'
alias cco='claude --model opus'
alias ccs='claude --model sonnet'

# Alias com pipe útil
alias ccgit='git diff | claude -p "resuma estas mudanças"'
alias ccreview='claude -p "revise este arquivo" <'

A wrapper is a shell script that combines Claude Code with other tools. Unlike an alias (which is just a shortcut), a wrapper can include logic: check conditions, process output, save it to a file.

Practical examples: a script that runs git diff, passes it to Claude Code for review, and saves the result to a Markdown file. Or a script that takes a log file, sends it to Claude Code to diagnose, and opens the result in the editor.

#!/bin/bash
# review-pr.sh - Review automatizado de PR
DIFF=$(git diff main...HEAD)
if [ -z "$DIFF" ]; then
  echo "Nenhuma mudança encontrada."
  exit 0
fi
echo "$DIFF" | claude -p "Revise este diff.
Aponte: bugs, melhorias, e se segue os padroes do projeto.
Formato: markdown com seções." > review.md
echo "Review salvo em review.md"

The simplest way is to run Claude Code in the integrated terminal from VS Code (Ctrl+`). You see the code above and chat with Claude below. Better yet, use two side-by-side panels: editor + terminal with Claude Code.

Anthropic also offers a official Claude Code extension for VS Code that integrates more deeply: the agent appears as a side panel, can reference open files, and edits appear in the editor in real time.

{
  "terminal.integrated.defaultProfile.linux": "bash",
  "terminal.integrated.fontSize": 13,
  "editor.formatOnSave": true,
  "workbench.panel.defaultLocation": "right"
}

O tmux (or screen) and is the perfect partner for Claude Code if you work on remote servers or want sessions that don't die. You open one pane with Claude Code, another with your editor, and can disconnect and reconnect at any time.

A classic setup: tmux new-session -s dev, splits into two panes (Ctrl+B %), run claude in one and edit in the other. If you need to leave, Ctrl+B d disconnects without killing it. tmux attach -t dev reconnects.

# criar sessão
tmux new-session -s claude-dev

# dividir em dois panes
Ctrl+B %     # split vertical
Ctrl+B "     # split horizontal

# rodar claude no pane esquerdo
claude

# desconectar (claude continua rodando)
Ctrl+B d

# reconectar depois
tmux attach -t claude-dev

Create a repository of dotfiles with: .bashrc/.zshrc (aliases), ~/.claude/CLAUDE.md (global preferences), ~/.claude/settings.json (global config), and a install.sh that creates the symlinks.

With versioned dotfiles, setting up your machine or switching computers is no longer a headache. Clone the repo, run the installation script, and in 5 minutes your Claude Code is configured exactly as before.

The complete setup brings all the pieces together: aliases in the shell for speed, VS Code with an integrated terminal for visual context, tmux for persistent sessions, dotfiles for portability, and Global CLAUDE.md for preferences that apply to every project.

The ideal daily rhythm: open tmux, run ccr (alias for claude --resume) to pick up where you left off, work for 1-2 hours, commit checkpoints, and when the context fills up, start a new session. Each day you improve the setup: a new alias here, a rule in CLAUDE.md there. In a week, the workflow is visibly faster than on day 1.

Setup diário com Claude Code:
[x] Aliases no .bashrc/zshrc (cc, ccr, ccp)
[x] VS Code com terminal integrado
[x] tmux para sessões persistentes
[x] CLAUDE.md global com preferências pessoais
[x] CLAUDE.md por projeto com stack e regras
[x] .claudeignore protegendo secrets
[x] settings.json com allowedTools afinados
[x] Dotfiles no git para portabilidade
[x] Ritmo: resume → trabalha → commit → repete