🏠 Back to Blog

Skip the Terminal (And 8 Other Claude Code Tricks for Non-Technical Users)

Author: Hannah Stulberg | Published: 2026-01-01

9 tips from 350+ hours of Claude Code use. The core problem: most AI tools require enormous effort to provide enough context for useful output.

The 9 Tricks

1. The Terminal Is a Black Box – Use an IDE

The standalone terminal is intimidating; you can’t see files, preview docs, or review changes
An IDE gives you file browser, text editor, and terminal in one window
Benefits: see file structure, preview markdown, review changes visually, access hidden .claude/ folder
Hannah uses Cursor, but VS Code/Windsurf work too

2. Cursor Lets You Pick the Best Model

Cursor’s built-in chat runs prompts against different models (Claude, GPT, Gemini, Grok)
Test the same prompt across models, compare results, feed the better output back into Claude Code
Avoids single-model lock-in

3. Show Hidden Files

Claude Code stores configuration in the .claude/ folder containing:
- Skills – markdown files that teach Claude specialized knowledge (auto-invoked)
- Commands – shortcuts triggered by /command-name (must be explicitly invoked)
- Agents – specialized AI personalities with isolated context
- CLAUDE.md – project context, preferences, workflow

4. Drag and Drop Files

Drag images or documents directly into Claude Code’s command line for analysis
Most shared files don’t need permanent saving

5. Run Parallel Sessions

Open multiple terminals for separate Claude Code sessions
Each gets its own context window dedicated to one task
Mixing unrelated tasks in one session degrades output quality
Rename terminals by task for easy identification

6. Split Terminals

Split terminal views to monitor 2-3 sessions at once
See immediately when a task completes

7. Watch the Status Line

Shows: model, working directory, context usage, session cost
Manually compact (/compact) at 50-60% usage, don’t wait for auto-compaction at the limit

8. Stop Typing – Talk Instead

Use Wispr Flow for voice dictation
Voice removes friction – explain conversationally instead of carefully typing

9. Every Session Is a Chance to Teach Claude

After every session ask: “Could I make this faster next time?”

Same explanation twice? Add it to CLAUDE.md
Same prompt sequence? Turn it into a command
Needs specialized context? Build a skill or agent
Getting 1% better daily compounds fast