15 Things I Wish I Knew Earlier

1. Stop Launching Claude and Then Typing

The gap: You open Claude Code, wait for it to load, THEN type your first instruction. Every single time.

The fix: Do it all in one shot from the terminal.

claude "Review the auth module for security gaps"

It launches and immediately starts working. No warmup.

Add a name so you can find it later:

claude -n "auth-review" "Check the login flow for vulnerabilities"

Name + initial prompt + go. By the time the session is live, it's already working. You land running.

2. Session Names Are Status Messages

The gap: You're juggling three sessions. You try to resume one and see a list of cryptic IDs or random first messages. Which one was which?

The fix: Name your sessions. But the real trick is updating the name as you go.

/rename "auth - building token refresh"
/rename "auth - waiting on API review"
/rename "auth - DONE, ready to merge"

The name shows in the resume picker. When you have multiple sessions going, you see the current state of each one at a glance.

Name at startup too:

claude -n "payment-v2"

3. The Session Picker Has Hidden Controls

The gap: You resume sessions by scrolling a list.

The fix: Type claude --resume and use these keys:

It's a session manager, not just a list.

4. Branch Your Conversations

The gap: You want to try a risky approach but don't want to pollute your working session.

The fix:

claude --resume my-session --fork-session

New session, branched from the old one. Original untouched. Dead end? Go back. It works? Keep the fork.

Git branches for conversations.

Mid-session, you can also type /branch (or its alias /fork) to branch from where you are right now.

5. Your Context Window Is Running Out? Focus It

The gap: Long session. Claude starts “forgetting” earlier context. You lose quality or start a new session and lose everything.

The fix:

/compact focus on the authentication flow and the test failures from step 3

This compresses the conversation but keeps what you told it to focus on. Fresh context window with the important stuff preserved. You don't have to choose between continuity and quality.

6. Shell Commands as Conversation Context

The gap: You run a command in another terminal, copy the output, paste it into Claude, explain what it means.

The fix: Just type ! before the command:

! git log --oneline -10
! npm test
! cat error.log

Output lands directly in the conversation. Claude sees it, reasons about it. No copy-paste, no explaining. Just bang-command and move on.

7. Claude as a Unix Pipe

The gap: You need a quick answer but don't want to start a whole session.

The fix: Print mode.

cat build-errors.txt | claude -p "what went wrong?"
git diff | claude -p "write a commit message" > commit-msg.txt
git diff | claude -p "any security issues?" | mail -s "Review" team@co.com

The -p flag means: answer and exit. No interactive session. Pipe in, pipe out. Build Claude into your shell workflows, scripts, CI/CD.

8. Keyboard Shortcuts That Change Everything

These are the ones I use constantly:

9. Side Questions That Don't Interrupt

The gap: Claude is in the middle of a big task. You have a quick question. If you type it, you derail the work.

The fix:

/btw what's the name of that config file?

Uses cached context (cheap). Gives you one answer. Does not go into conversation history. It's like whispering a question while someone is working — they answer and keep going.

10. CLAUDE.md Is Your Project's Persistent Brain

The gap: Every new session, you re-explain your project conventions. “We use TypeScript.” “Tests go in __tests__.” “Don't touch the legacy folder.” Over and over.

The fix: Put it in CLAUDE.md at your project root. Claude reads it automatically on every session.

But here's what most people don't realize:

a) Nested CLAUDE.md files

Put API rules in src/api/CLAUDE.md. Frontend rules in src/ui/CLAUDE.md. They load only when Claude works in those directories.

b) Import files with @

See @README for project overview
Follow @docs/coding-standards.md

c) Path-specific rules

Put rule files in .claude/rules/ with path-scoped frontmatter:

---
paths:
  - "src/api/**/*.ts"
---
Always validate input. Use try-catch. Log to the monitoring service.

These rules only activate for matching files.

d) Global instructions

Your personal instructions go in ~/.claude/CLAUDE.md. Applied to all projects. Your coding style, preferences, patterns — write once, always active.

11. Stop Clicking “Yes” for Safe Commands

The gap: Claude asks permission for every action. Reading files? “Yes.” Running tests? “Yes.” Git status? “Yes.” You become a permission-clicking machine.

The fix: In .claude/settings.json:

{
  "permissions": {
    "allow": [
      "Bash(npm test)",
      "Bash(git status)",
      "Bash(git diff *)",
      "Bash(git log *)",
      "Read"
    ]
  }
}

Now Claude reads files and runs safe commands without asking. You only get prompted for things that actually need your attention.

Or during a session: just hit Shift+Tab to cycle to acceptEdits mode. All file edits auto-approved.

12. @ for Instant File References

The gap: You type “look at the file at src/components/auth/login.tsx” and hope Claude finds it.

The fix: Type @ and it triggers file path autocomplete.

Check @src/components/auth/login.tsx for the bug

Direct reference. No ambiguity. Works mid-sentence.

13. Custom Agents: Build Your Own Team

The gap: You keep giving Claude the same specialized instructions for recurring tasks.

The fix: Create an agent file in .claude/agents/, for example security-reviewer.md:

---
description: "Reviews code for security vulnerabilities"
tools:
  - Read
  - Grep
  - Glob
---
You are a security reviewer focused on OWASP top 10...

Claude can spawn this as a subagent when the task fits. Build a library of agents for things you do repeatedly: code reviewer, test writer, documentation generator. Check the docs for the full set of frontmatter options.

14. Visual Session Tracking with /color

The gap: Multiple terminal tabs, multiple sessions, they all look the same.

The fix:

/color red
/color blue
/color green

Changes the prompt bar color. Red for production work. Blue for experiments. Green for tests. You see at a glance which session is which.

15. The Quick Returns

Quick things that punch above their weight:

Putting It Together: Real Workflows

git diff | claude -p "any bugs or security issues?"

claude -n "risky-refactor"

claude --add-dir ../shared-libs

git diff --staged | claude -p "write a commit message" > .git/COMMIT_EDITMSG

Where This All Lives

Your sessions, memory, and settings are stored locally at:

~/.claude/

Sessions are persistent. They don't expire. You can resume any session from any time.