---
title: "Discussion on \"Going Deep on Claude Code: 6 Hidden Features Most Developers Miss\" | Hashnode"
description: "Discussion on \"Going Deep on Claude Code: 6 Hidden Features Most Developers Miss\". Intro\nI was using Claude Code wrong for weeks.\nNot broken-wrong. It worked fine. I'd describe a task, Claude would write code, I'd tweak it, move on. Totally reasonable workflow. Except I was treating"
url: "https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Going Deep on Claude Code: 6 Hidden Features Most Developers Miss](https://brightgirl.hashnode.dev/going-deep-on-claude-code-6-hidden-features-most-developers-miss?utm_source=hashnode&utm_medium=feed)

Intro I was using Claude Code wrong for weeks. Not broken-wrong. It worked fine. I'd describe a task, Claude would write code, I'd tweak it, move on. Totally reasonable workflow. Except I was treating

May 10 · 5 min read · brightgirl.hashnode.dev  
Read the article

## Written by

[Victoria Fonareva](https://hashnode.com/@brightgirl)

@brightgirl · Warsaw, Poland

  
[View profile](https://hashnode.com/@brightgirl)

Software Engineer at Yandex Fintech | Go Developer

Building payment infrastructure at Yandex. Focused on backend scalability, Go, and practical LLM applications. I value high-density information and efficient execution.

## Responses 5

Markdown supported · ⌘↵ to post

[Daan Hoekstra](https://hashnode.com/@daanhoekstra)

[May 13](https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb/comment/6a0478b2a0c1540277367c9e)

The thing I'd add: /batch paired with worktrees changes the economics of refactoring entirely. Tasks that felt too risky to delegate to an agent because of scope become tractable when each branch is fully isolated. I've started treating it less like an assistant and more like a parallel workforce with a shared standup.

[Victoria Fonareva](https://hashnode.com/@brightgirl)

[May 13](https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb/comment/6a0478b2a0c1540277367c9e#reply-6a04a08ea0c15402774da572)

Spot on! The worktrees + /batch combo is the final boss of AI-assisted refactoring. It completely solves the 'context pollution' problem when you’re trying to do ten things at once. Love the 'parallel workforce' mental model — it really shifts the perspective from 'chatting with a bot' to 'orchestrating a sprint'. Definitely experimenting more with this as projects get messier. Thanks for the tip!

[Ali Abubakar](https://hashnode.com/@aliyuindibe1)

[May 11](https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb/comment/6a01f752fca21b0d4b3d96f6)

This is gold, My dearVictoria 👏

Love how you broke down the stuff that actually changes the workflow, not just the surface-level tips. The CLAUDE.md + “make the agent write its own instructions” combo is the part that clicked for me too, it’s the difference between using Claude as a tool vs actually building a second brain for the project.

The `!` trick alone has saved me so much tab-switching. And plan mode? Should be default for anything beyond “fix this typo” 😅

Thanks for putting this together so clearly. Definitely sharing it with the team.

Curious, which one of these features changed your day-to-day the most since you started using them consistently?

Aliyu\_indibe1

[Victoria Fonareva](https://hashnode.com/@brightgirl)

[May 11](https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb/comment/6a01f752fca21b0d4b3d96f6#reply-6a01fd98fca21b0d4b41bfa4)

Thanks for the support, Ali!

Totally agree about the 'second brain' — that's the goal. For me, point #5 (self-updating instructions) is the most impactful. It feels like the project starts to 'remember' things, and I can focus purely on architecture.

[Ali Abubakar](https://hashnode.com/@aliyuindibe1)

[May 11](https://hashnode.com/posts/going-deep-on-claude-code-6-hidden-features-most-developers-miss/6a00be2fe3eebc2e20aaedbb/comment/6a01f752fca21b0d4b3d96f6#reply-6a020c54fca21b0d4b4c5b87)

Exactly, once it starts remembering, it feels like you’ve got a teammate who actually learns from the project instead of resetting every session. That shift from “managing prompts” to “working on architecture” is huge.

And yeah, feel free to steal “second brain” 😄 Happy if it sticks.

I’ll keep an eye out for any follow-up you write on scaling [http://CLAUDE.md](http://claude.md/), that’s the part most people struggle with once projects get messy.

Thanks again for sharing this
