Anthropic shipped 125 settings for Claude
The official docs cover 40
One developer found the other 85 and his API bill dropped from $340 to $87
- not by using a cheaper model
- not by writing shorter prompts
just by moving one line in a config file to the right place
> memory scoped per project → past clients never bleed into new work
> Extended Thinking on Light by default → 18–25% fewer Opus tokens in week one
> cache_control moved to the right line → the fix that turned a $340 bill into $87
> plugins and MCP servers toggled off when idle → saved 25–40K tokens per session
> per-project model override → Haiku for docs, Sonnet for infra, Opus only where it matters
most Claude users are running a $100/month tool at 30% of its actual capability
a prompt I've been using a lot recently:
implement <SPEC> and while you do, keep a running implementation-notes.html file (or markdown) with decisions you had to make weren't in the spec, things you had to change, tradeoffs you had to make or anything else I should know
Mistakes happen. As a team, the important thing is to recognize it’s never an individuals’s fault — it’s the process, the culture, or the infra.
In this case, there was a manual deploy step that should have been better automated. Our team has made a few improvements to the automation for next time, a couple more on the way.
I accidentally discovered how to compress a month of research into 3 hours.
A founder at a YC company showed me his Claude setup. I thought he was just fast. Then I watched him build an entire go-to-market strategy for a market he'd never worked in before.
Here's exactly what he did:
First: he didn't ask Claude to "research the market."
He fed it 8 competitor landing pages, 3 earnings call transcripts, 12 customer reviews, and a Reddit thread of complaints.
Then he asked one question:
"What does every successful player in this market understand that their customers never say out loud?"
Not "summarize these." Not "analyze the competition."
The unspoken insight. The thing that takes founders 2 years of customer calls to figure out.
But the next part is what broke my brain.
He followed up with:
"Now show me the 3 assumptions this entire market is built on, and what would have to be true for each one to be wrong."
In 15 minutes he had the attack surface of an entire industry.
The blind spots. The fragile consensus. The opening nobody was talking about.
Most founders spend 6 months doing customer discovery just to find one of those.
Then he did something I've never seen before.
He asked:
"Write 5 questions a world-class investor would ask to destroy this business idea, then answer each one using only the evidence in these documents."
He spent the next 2 hours stress-testing every assumption. Every weak answer triggered a follow-up:
"What's the strongest version of this argument and where does it still break?"
By hour 3, he had a strategy deck that felt like it came from someone who'd spent a decade in the space.
The tool didn't change. The questions did.
Most people treat Claude like a faster Google.
These founders are using it like a thinking partner who has read everything and has no ego about being wrong.
The difference between 3 hours and 3 months isn't the amount of information.
It's knowing which questions actually matter.
I'm excited to announce Context Hub, an open tool that gives your coding agent the up-to-date API documentation it needs. Install it and prompt your agent to use it to fetch curated docs via a simple CLI. (See image.)
Why this matters: Coding agents often use outdated APIs and hallucinate parameters. For example, when I ask Claude Code to call OpenAI's GPT-5.2, it uses the older chat completions API instead of the newer responses API, even though the newer one has been out for a year. Context Hub solves this.
Context Hub is also designed to get smarter over time. Agents can annotate docs with notes — if your agent discovers a workaround, it can save it and doesn't have to rediscover it next session. Longer term, we're building toward agents sharing what they learn with each other, so the whole community benefits.
Thanks Rohit Prsad and Xin Ye for working with me on this!
npm install -g @aisuite/chub
GitHub: https://t.co/OCkyxXQMCq
Don't be that teammate who blindly refactors code and only makes things worse.
Let's look at some good vs bad refactoring patterns with real examples 🧵