1
2 Comments

I Spent Two Months Using Claude Code Wrong

I used Claude Code for weeks before stumbling onto a setting that completely changed how I work with it. Most people don't know it's there.

Under /config, there's an "output style" option. Default is fine, but switching to "Learning" made a real difference for me. Instead of just getting code and moving on, I started understanding why certain approaches were better. It's slower, sure, but my retention is way better now.

For repetitive automation tasks, I keep it on "Proactive" mode. Claude Code actually anticipates next steps instead of waiting to be told.

The part that made me laugh: this is documented, but buried. I probably ran the tool 50+ times before noticing.

If you're building with AI coding tools, it's worth spending 10 minutes just exploring settings. The defaults are rarely optimized for your specific workflow. What settings have you found that actually changed how you work?

on June 15, 2026
  1. 1

    The real workflow upgrade I found is the project context file Claude Code reads before every session (CLAUDE markdown file in the project root). For automation work especially, once I spelled out the error handling patterns — what to retry, what to log, when to bail — I stopped re-explaining the same things 50 times across sessions.

    The settings menu is useful but the project context file is where the real customization lives for repetitive builds. Takes ~30 min to set up properly and saves hours. Worth looking into alongside the config options you mentioned.

  2. 1

    ok i did NOT know about the Learning output style — just checked /config,
    adding this now. i used Claude Code to build my entire first app as a
    non-coder, and honestly "getting code and moving on without understanding
    it" describes me perfectly lol. the retention point is real, i've shipped
    stuff i couldn't explain.

    haven't touched the settings nearly enough — definitely guilty of running
    it 50+ times on defaults. thanks for this, genuinely useful.

Trending on Indie Hackers
6 weeks solo, 2 rejections, finally live but nobody told me marketing would be this hard User Avatar 140 comments I spent more time setting up cold email than actually selling. Here is what fixed it. User Avatar 38 comments I just wanted to taste AI coding tools. A week passed. User Avatar 24 comments I built a PDF API because every team I know has a haunted corner of their codebase they never want to open User Avatar 19 comments A pattern I keep seeing in EdTech: traffic isn't usually the problem. User Avatar 17 comments Building LinkCover – Day 3: Payment is live. No more building, time to sell. User Avatar 16 comments