Here are my tips for getting the most out of Claude Code, including a custom status line script and Claude Code running itself in a container. Also includes the dx plugin: skills for everyday dev workflows.
Auto-invoked ships a router so the right skill fires automatically as you prompt. No remembering which skill to call.
Normal is the plain upstream plugin, installed as-is. You invoke its skills yourself.
The plugin> /plugin marketplace add ykdojo/claude-code-tips> /plugin install dx@ykdojoAuto-invocation> /plugin marketplace add flowy-sh/flowy-core> /plugin install flowy-core> /plugin install flowy-dx
Repo: ykdojo/claude-code-tips
What's inside
Here are my tips for getting the most out of Claude Code, including a custom status line script and Claude Code running itself in a container. Also includes the dx plugin: skills for everyday dev workflows.
📺 Quick demo - See some of these tips in action with a multi-Claude workflow and voice input:
You can customize the status line at the bottom of Claude Code to show useful info. I set mine up to show the model, current directory, git branch (if any), uncommitted file count, sync status with origin, and a visual progress bar for token usage. It also shows a second line with my last message so I can see what the conversation was about:
Opus 4.5 | 📁claude-code-tips | 🔀main (scripts/context-bar.sh uncommitted, synced 12m ago) | ██░░░░░░░░ 18% of 200k tokens
💬 This is good. I don't think we need to change the documentation as long as we don't say that the default color is orange el...
This is especially helpful for keeping an eye on your context usage and remembering what you were working on. The script also supports 10 color themes (orange, blue, teal, green, lavender, rose, gold, slate, cyan, or gray).
To set this up, you can use this sample script and check the setup instructions.
There are a bunch of built-in slash commands (type / to see them all). Here are a few worth knowing:
Check your rate limits:
Current session
█████████▌ 19% used
Resets 5:39pm (America/Vancouver)
Current week (all models)
██▌ 5% used
Resets Sep 6 at 9:59am (America/Vancouver)
Current week (Fable)
█████ 10% used
Resets Sep 6 at 9:59am (America/Vancouver)
If you want to watch your usage closely, keep it open in a tab and use Tab then Shift+Tab or ← then → to refresh.
Manage Claude's native browser integration:
Status: Disabled
Extension: Installed
❯ Manage permissions
Reconnect extension
Enabled by default: No
Usage: claude --chrome or claude --no-chrome
Manage MCP (Model Context Protocol) servers:
Manage MCP servers
3 servers
User MCPs (/Users/ykdojo/.claude.json)
❯ playwright · ✔ connected · 24 tools
claude.ai
→ Show unused connectors (1)
Built-in MCPs (always available)
computer-use · ◯ disabled
View your usage statistics with a GitHub-style activity graph:
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug
················································▒▒▓▓
Mon ················································▒▓█
················································██░
Wed ················································▒░░
···············································█░▒█
Fri ···············································░▒·█
···············································▓▓▓░
Less ░ ▒ ▓ █ More
Favorite model: Fable 5 Total tokens: 755.6m
Sessions: 157 Longest session: 16h 45m 11s
Active days: 24/26 Longest streak: 15 days
Most active day: Aug 27 Current streak: 9 days
Your input and output are ~12x the tokens in Moby-Dick
Clear the conversation and start fresh.
I found that you can communicate much faster with your voice than typing with your hands. Using a voice transcription system on your local machine is really helpful for this.
On my Mac, I've tried a few different options:
You can get more accuracy by using a hosted service, but I found that a local model is strong enough for this purpose. Even when there are mistakes or typos in the transcription, Claude is smart enough to understand what you're trying to say. Sometimes you need to say certain things extra clearly, but overall local models work well enough.
For example, in this screenshot you can see that Claude was able to interpret mistranscribed words like "ExcelElanishMark" and "advast" correctly as "exclamation mark" and "Advanced":
I think the best way to think about this is like you're trying to communicate with your friend. Of course, you can communicate through texts. That might be easier for some people, or emails, right? That's totally fine. That's what most people seem to do with Claude Code. But if you want to communicate faster, why wouldn't you get on a quick phone call? You can just send voice messages. You don't need to literally have a phone call with Claude Code. Just send a bunch of voice messages. It's faster, at least for me, as someone who's practiced the art of speaking a lot over the past number of years. But I think for a majority of people, it's going to be faster too.
A common objection is "what if you're in a room with other people?" I just whisper using earphones - I personally like Apple EarPods (not AirPods). They're affordable, high quality enough, and you just whisper into them quietly. I've done it in front of other people and it works well. In offices, people talk anyway - instead of talking to coworkers, you're talking quietly to your voice transcription system. I don't think there's any problem with that. This method works so well that it even works on a plane. It's loud enough that other people won't hear you, but if you speak close enough to the mic, your local model can still understand what you're saying. (In fact, I'm writing this very paragraph using that method on a flight.)
Update: Claude Code now has a built-in voice mode. I tested it and it works well, but I still personally use a local model because I find it faster.
This is one of the most important concepts to master. It's exactly the same as traditional software engineering - the best software engineers already know how to do this, and it applies to Claude Code too.
If you find that Claude Code isn't able to one-shot a difficult problem or coding task, ask it to break it down into multiple smaller issues. See if it can solve an individual part of that problem. If it's still too hard, see if it can solve an even smaller sub-problem. Keep going until everything is solvable.
Essentially, instead of going from A to B:
View @ykdojo’s profileThe easiest way to run multiple Claude Code sessions, each in its own container, with a dashboard to manage them all. Quick setup with battle-tested sensible defaults and skills. See architecture.md for design details.
@ykdojoFAQ
dx is a Claude Code plugin of 9 hand-picked skills with a FLOW.md router. Install it once and the right skill fires as you prompt, with no slash command to remember. It is built for development work. It includes gha, half-clone, handoff. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it