All Articles
When a proofreading request comes back as a rewrite: keeping the original wording
Ask for proofreading and you often get a polished replacement instead. Fixing the output shape first, splitting edits into three layers, and showing one keep-and-change example pair will hold on to the author's sentence endings and word order.
What I Stop Doing Before I Hit Claude's Limit — Rebuilding a Day Around the Five-Hour Window
Claude's usage recovers on a five-hour window, but that window doesn't start on the clock — it starts with the first message you send. Here's how I reordered my working day so I stop before the limit stops me.
Where to Put an Instruction That Keeps Coming Back: Chat, Style, Settings File, or Hook
No comments, please. Do not translate the product name. When an instruction drifts back a few turns later, the fix is usually the location, not the wording. I compared the same sentence across four layers and settled on a rule for which instruction belongs where.
Picking Up Where You Left Off: When to Lean on Claude's Memory and When to Ask It to Search
Claude's memory and past-chat search are two different mechanisms. How to tell which one answered you, why project boundaries block searches, why deleting a chat leaves its memory behind, and which plans get what.
When Adding Files Makes Your Claude Project Answer Worse
You upload more material to a Claude Project and the answers get vaguer, not sharper. The cause is overlap, not volume. Here is a small script that measures how much your knowledge files repeat each other, and the three questions I use to decide what stays.
The 30-Day Session Cleanup Is Fixed, and It Made Me Rethink Where I Keep Records
Claude Desktop and Cowork sessions were quietly disappearing after 30 days until v2.1.248 fixed it. Here is how to check your own setup, what the new setting actually caps, and a small journal script that keeps one line per run outside the session.
What to Settle Before Watermarked Claude Text Ships Inside Your App
Claude models released on or after August 2, 2026 embed watermarks in generated text and attach C2PA-signed provenance metadata to files. Here is how I redrew the line for shipped copy, plus a measured look at where image metadata disappears and a submission gate that keeps provenance reproducible.
Claude for Open Source: reading the criteria, and the trap that undercounts your own work
Claude for Open Source grants six months of Max 20x. Before the 5,000-star line makes you close the tab, here is how the two application tracks actually work, and how to check whether your last three months are being counted correctly.
Using Claude's Reflect Monthly Review to Tune a Solo Dev Rhythm
How to read Claude's new Reflect monthly review as a planning tool for the month ahead rather than a report card, grounded in the day-to-day rhythm of solo development.
When a Connector Starts Slowing Down at Night: A Health-Aware Circuit Breaker for Solo Automation
Seeing connector errors and latency is only half the job — the other half is deciding when to route around them. This is my implementation of a circuit breaker that opens on error rate and p95, with runnable Python and notes on wiring it into nightly jobs.
Claude Card Declined: Narrowing Down Who Actually Blocked the Payment
When your card is declined on Claude Pro or Max, the block comes from your issuing bank, from Stripe, or from Anthropic. Here is how the decline codes a merchant actually sees map to the three checks you can run yourself — international blocks, 3-D Secure, and postal code mismatches.
Claude Card Declined: A Complete Troubleshooting Guide for Pro, Max, and API Users
When Claude tells you 'Your card was declined,' the cause is rarely obvious from the error text alone. This guide separates the three layers where a decline actually happens — your issuing bank, Stripe's fraud engine, and Anthropic's account state — and walks you through fixes plus fallback payment methods that almost always get the charge through.