Anthropic raised the thresholds this week. Here is what actually changed, what did not, and how to make your Claude session go further. **What changed (May 06):** - Claude Code 5-hour session limits **doubled** for Pro, Max, Team, and Enterprise. - Peak-hours throttle on Claude Code **removed** for Pro and Max. - Claude Opus API rate limits raised "considerably." - Powered by a new SpaceX compute deal: 300+ MW of capacity, around 220,000 NVIDIA GPUs. **What did NOT change:** - Weekly limits. If you were hitting the weekly cap last month, you will still hit it this month. - The change buys you more in a single session, not more across a week. --- ## 5 ways to stretch your Claude session (desktop users) These work on Claude.ai and the desktop app. No code required. **1. Use Projects, stop re-pasting the same context.** If you keep pasting the same brief, doc, or code file into every new chat, move it into a Project once. Every conversation inside that Project sees those files automatically. You stop burning your session limit re-uploading the same information, and Claude stops re-reading it. **2. Start a new chat when the topic changes.** Every message in a long chat sends the entire history back to Claude. After 30 or 40 turns, you are paying (in session usage and in speed) for the first message every single time. When you switch topic, start fresh. **3. Pick the right model for the task.** Haiku for quick lookups, summaries, and short questions. Sonnet for normal day-to-day work. Opus only when the task is genuinely hard (architecture, dense reasoning, long multi-step analysis). Most people leave Opus on for everything and burn through the limit much faster than they need to. **4. Be specific in your first message.** Vague prompts trigger 5 rounds of clarification. One precise prompt with full context and constraints lands the answer in one shot. Spend 30 seconds writing the prompt, save 10 minutes of back and forth. **5. Use Artifacts instead of asking for full rewrites.**

Update from Saturday: Amazon terminated my KDP account. Not for this book — an unrelated nostalgia title I had on KDP tripped their AI-content review. Lifetime ban, royalties forfeit, no reopening. The Amazon link in my last post above is dead. The book itself is fine. Just not on Amazon. Pivoted to direct sales on Payhip today. ~45 min to get there. PDF + EPUB bundle, DRM-free, EU VAT handled by the platform. ~90% margin vs Amazon's ~30% — which honestly works out better long-term. For this community — code SKOOL, 25% off, expires Sunday 11 May: https://payhip.com/b/VpTj3?coupon=SKOOL → €18 Free Chapter 9 (the same PDF I was DM'ing on request — now self-serve): https://payhip.com/b/9TWtN @Gareth Parkes — thank you for the KU offer. Book's no longer on KU but if you still want to read and review, DM me and I'll send a copy directly. @Ellie Davis — thank you. With Amazon gone, reader feedback (Goodreads, LinkedIn, even a sentence in this thread) is the social proof doing the heavy lifting now. ▎ Also live on the same store: The Claude Playbook — the hands-on guide to ▎ Claude from first prompt to production code. €19, same SKOOL code → ▎ €14.25. Built from the curriculum many of you already know. ▎ https://payhip.com/b/Dk3OB?coupon=SKOOL

▎ EDIT (4 May): Amazon terminated my KDP account on Saturday. Book is now at https://payhip.com/b/VpTj3 — see [this post](link to your new update) for the story. I shipped a 305-page book this week. "Rewiring Corporate Finance", a blueprint for what the finance function becomes when AI moves from pilot to load-bearing. 12 chapters, 9 custom diagrams, EU AI Act compliance map and a 12-month execution plan for CFOs When I say I used Claude, people assume it wrote the book. It didn’t. I have over 15 years inside finance at Philips and Vodafone.The seat and the judgment are mine. What Claude actually did was this: 1. Pressure-tested the thinking: Every chapter had a thesis. I made Claude argue against it before I wrote.Some ideas held. Others didn’t. 2. Cut the corporate voice: Anything that sounded like a consulting deck got flagged.The writing is tighter because of that. 3. Handled the messy production layer: Cover math. Spine width. EPUB. KDP formatting. Claude wrote the Python to turn the draft into something uploadable.That’s where most people get stuck. 4. Turned ideas into diagrams : I described the systems. It generated clean visuals I could actually use. What it didn’t do: The experience.The opinions.The calls on what goes agent-first vs stays human. If you’ve ever thought about writing a book: This is way more doable now than it was even a year ago. If you want, I can break down exactly how I went from idea to published. Just DM me. And if you’re building AI skills on top of your current finance role: Comment on this post and I’ll send you the PDF of Chapter 9. It covers: - the four literacies (finance, data, AI, programming) - the hybrid finance-developer profile - why the junior pipeline is going to change

4 days ago Anthropic just launched Claude Design (claude.ai/design). If you ship products but you're not a designer, this one's for you. Claude Design is a new surface built specifically for visual output (landing pages, UI, full page layouts) with a live preview and real iteration. So I pointed it at one of my own project. obikido.com my family calendar solution that lives inside WhatsApp. In 2 minutes I got the landing pages attached in the video 1. Went to claude.ai/design 2. Linked it to the related project in my Claude account — so it already had the full context: what Obikido is, who it's for, the tone of voice 3. One prompt: "improve the landing page" No brief. No reference sites. No screenshots. The project link did all the heavy lifting. You can judge the quality yourself, compare the live produciton site with the prototype in video. What I'm taking away: - Linking Claude Design to a project or repo is the unlock. I did zero prompt engineering and got something I'd ship. I will now pick some elements of the proposed design and deploy them later - It's fast enough that there's no excuse to ship a weak landing page anymore :) even for v1. - For solo founders and indie devs, this collapses a week of designer back-and-forth into one prompt. Honestly this could kill Figma. I'm going to run the same exercise on a couple more of my pages. If you try it on yours, drop the before/after in the comments. Vincent

Hey everyone! 👋 +20 members and already spread across the globe, pretty cool to see. I'm curious to know more about you all. Feel free to share: ○ What are you working on right now? ○ What's your main goal with Claude? ○ What's your biggest roadblock? The idea here is simple: we unlock each other's roadblocks. Your challenge might be something I already solved, and vice versa. I built this structured curriculum to give you a solid foundation, but I also have more ideas coming: ○ Project-focused modules using Claude end to end ○ Tips and tricks from real daily usage ○ Deep dives on topics you request So do not hesitate. Ask questions, share your projects, request a deep dive. This community grows when we all contribute. What are you working on? What do you want to learn? Drop it below 👇