I’ve used Claude Code for 100+ hours building MVPs. Most developers...

61 views Jul 05, 2025 ~2 min read

                            1
                        
I’ve used Claude Code for 100+ hours building MVPs.

Most developers are missing the best features.

Here are 10 tricks that will change how you build ↓

                            2
                        
1/ Use planning mode before EVERYTHING

- hit Shift+Tab twice to enter planning mode
- I plan every feature here first
- no code gets written until the plan is solid
- saves me hours of refactoring later

                            3
                        
2/ Create custom commands for repetitive tasks

- Make a /claude/commands folder
- Create markdown files for common workflows

I have commands for:
- Security audits
- Documentation generation
- Code reviews

Like having a senior dev on speed dial

3/ Use the init command on every project

- Run init in your project root
- It creates a claude.md file with your full codebase structure
- Claude remembers this context in every session

Best lightweight documentation you’ll ever get

                            5
                        
4/ Master the headless mode

- Use claude -p from the command line
- I pipe audit results directly to Claude:

npm audit | claude -p "prioritize these vulnerabilities"

Instant security analysis without opening the UI

                            6
                        
5/ Connect your IDE for visual debugging

- Claude auto-detects VS Code and Cursor
- When I highlight code, it knows exactly what I’m working on
- Screenshots of bugs get analyzed instantly

Two-way communication changes everything

                            7
                        
6/ Use “think” keywords for complex problems

- Add "think" or "ultrathink" to your prompts
- Claude spends more time reasoning
- Better solutions for architecture decisions
- Worth the extra tokens for critical features

                            8
                        
7/ Images are your secret weapon

- Drop screenshots directly into Claude
- Use Control+V on Mac (not Command+V)

I use this for:
- UI bug fixes
- Design inspiration
- Error message analysis

                            9
                        
8/ Interrupt and fork conversations

- Hit Escape to stop Claude mid-response
- Hit Escape twice to go back to previous messages

Perfect for when Claude goes off-track
Clean way to restart without losing context

                            10
                        
9/ Feed it entire folders for context

- Claude works better with full project context
- I upload entire folders from past MVPs
- It instantly understands my coding style and logic

Especially useful for similar projects

                            11
                        
10/ Always ask for code reviews

After Claude writes code, ask:
“Can you review what you just wrote?”

- It catches its own mistakes surprisingly well
- Feels like having code and QA in one step

                            12
                        
11/ Use URLs for live documentation

- Paste documentation URLs directly
- Claude fetches the latest version
- No more outdated tutorials or deprecated methods
- You’re always working with current best practices

                            13
                        
12/ Claude Code isn’t just a coding tool
It’s a thinking partner.

I use it for:
- Architecture planning
- Problem-solving
- Learning new concepts
- Code optimization

You’re probably going to forget this.
And all the other AI dev workflows I’ve shared this week.

So I started a weekly newsletter
Quick recap every Sunday on AI dev, vibe coding, and MVP building.

Subscribe here:
aimvpweekly.beehiiv.com

I’ve used Claude Code for 100+ hours building MVPs. Most developers...

Actions

What You Can Do

Actions

What You Can Do

More in AI & Machine Learning

More from @PrajwalTomar_