What do you think?

I have been a developer for about 20years and I am blown away by what I can acheive using ClaudeCode with Opus 5.5, as I presume most experienced devs are out there. I use it every day for work, and now have time to revisit some of those hobby projects I either started, and didnt finish, or never got round to.

But, I find that even though I can get more done in the same time, and it is not me writing the code, there is somehow still a drain on me mentally, like even though I did a whole weeks work before lunch, and my UI looks better than I could have done it myself, and the test coverage is close to perfect, it feels as though I am as tired as if I had done all that. Coupled with the feeling that because it is so productive it should always be doing something, so I might set a task going and then go eat dinner, and then check in after the meal, my brain is always on and always thinking of the next thing I can ask Claude to do.

Is anyone else experiencing a kind of feeling of burnout from the sheer pace of software productivity?

Claude Opus 5.5 is insane, that's all I've got to say.

No other AI comes close, I am on $20 plan and I can literally finish a whole BIG project and still have a lot of plan left.

Readable Layout puts your messages and Claude's answers in labeled boxes, turns its in-between notes into quiet lines, and ends each turn with a rule.

Here’s a quick demo of how it looks:

If you want to try it out, you can install it here:
/plugin marketplace add GarvitNangru/claude-code-mods
/plugin install readable-layout@garvit-mods

Let me know what you guys think.

Star it on github if you like it
https://github.com/GarvitNangru/claude-code-mods

and yeah that's about right

Wordpress has been the bane of my small biz existence for two years, so a couple of weeks ago I started the process of migrating off of it and rebuilding our two sites with Claude.

The results have been amazing. Not only does the whole site look much better, but I'm able to advance projects that were stalled because the cost of making them public via WP was too dreadful to contemplate.

I've hired Wordpress guys on Upwork, TopTal, etc. The friction of managing another person remotely to ship things was just too much. (We're a four-person boutique consultancy that specializes in HR technology, average client size orgs with 5k employees.)

The ability to realize my vision, I've come to understand, happens during the process of building. It's just how I work. I can't tell people to build something when the only way I know what it needs to be crystallizes during the process of creating it.

https://integralrecruiting.com/
https://systemadmininsights.com/

Now I'm building the operational infrastructure (CRM, time tracking, capacity planning, client portals) to get us off of Notion, spreadsheets, etc. It's a dream come true.

The Claude Code team posted how they review code now that Claude writes most of it.

What stood out:

- A Claude reviewer checks every PR. After they added it, PRs with real review comments went from 16% to 54%.
- PRs that needed 5 or more review rounds dropped from 8.9% to 1.5%.
- Low-risk changes, like docs, can merge with no human approval once the automated and security checks pass.
- An agent's approval never counts as a person's.
- If you prompted the agent, you count as one of the reviewers of its PR.
- One PR went through more than 50 review rounds overnight. Now, after 3 rounds, the reviewer tells the author to step back and rethink the approach.

Things you can copy today:

- Run /code-review and /security-review before you open a PR
- Keep a REVIEW.md with what matters in your code, and move comments you kee
- Cap review rounds at about 3

Their Code Review for GitHub PRs is also out of beta now, but only on Team and Enterprise.

Source Link

How do you review the code Claude writes? I'd like to read what works for you.

First post because I genuinely don’t know how many more times I can tell Claude to stop running 1500+ tests after making a small change. It takes like 2 hours to do each time and it’s gotten smarter to where it renames the background tasks it’s running to not say that it’s running tests. It only then admits it’s running the tests I told it not to when I notice it’s been stuck on some generic sounding background task for an hour.

Is anyone else struggling with this or have found a solution? I’ve changed my AGENTS.md and a bunch of other .md files in an attempt to stop it but every time it runs more then is like “you’re right, I ignored xxx.md and am running tests. Stopping now.”

Looking for any possible solutions as my project has been mostly at a standstill (from incessant test running) for the last couple of weeks.

Like many of you, I've been extensively using Claude Code over the last year-plus, and as I'm sure many of you can relate, it's been nothing short of life-changing. From developing dream applications, tools, games, and productivity to building workflows for my business, I've been able to do things I never thought possible.

But between the constant flow of hyper-optimization ideas for everything from my business, personal life, creative ideas, etc. I feel mentally burnt out more than I ever have in my life. It doesn't help when a new model drops, either. Suddenly you want to go back and refactor all your apps, test your current architectures, and see what the new model can replace or do better. It's a huge dopamine rush, but man, I feel like I'm running on this infinite treadmill sometimes that I just can't get off of. Is this AI psychosis? lol. Does anybody else feel the same?

Everything in CLAUDE.md gets loaded into every session. That includes the note about a bug you fixed last month and the naming rule for one folder you rarely touch. The file grows, the signal gets buried, and the rules that matter get followed less consistently.

Here’s how I’d split it:

Keep in CLAUDE.md: the package manager, the build/test/lint commands, architectural constraints the code doesn’t make obvious, conventions that apply to most changes, and mistakes worth remembering across tasks.

Keep in the prompt: the specific feature or bug, its acceptance criteria, and any temporary constraint that shouldn’t leak into unrelated work.

Scope the rest: if a rule only applies to part of the codebase, put it in .claude/rules/ with a path scope. A migration convention doesn’t need to load while you’re fixing CSS.

One more thing people miss: CLAUDE.md is guidance, not enforcement. If something must happen every time, like a check before a certain action, use a hook or an external validation step. Don’t rely on the model remembering a sentence.

The rule of thumb: if it applies to almost every task, make it persistent. If it applies to certain files, scope it. If it applies to one task, keep it in the prompt.

How are you organizing project instructions as your codebase grows: one CLAUDE.md, path-specific rules, or a mix?

I kept opening Claude's usage page to check where I was: how much of my 5-hour session was left, how close I was to the weekly limit. Ten times a day. It was driving me nuts.

So I took one of those cheap 3.5" USB screens people put in their PC cases, and with Claude Code I wrote a small program that shows exactly that. Two rings on the left: the 5-hour session and the week, with the time left before each reset. The PC on the right: GPU temperature, CPU, memory, disk, network.

Now I just glance down. I use it all day, every day, and honestly I love it.

How Claude helped: I built the whole thing with Claude Code. The vendor software for these screens is closed, so Claude wrote the driver for the screen's USB protocol, the drawing code, the tests and the Windows startup task with me. One fun problem: the screen is slow (a full image takes 1.2 seconds over USB), so the program draws everything in memory and only sends the parts that changed. That keeps it smooth at about 2% of one CPU core.

The real point of this post: none of this is hard. It's a small Python program. If you have Claude Code and one of these screens, you can build your own version with your own layout, pretty simply. That's what still amazes me about Claude.

If you'd rather just use mine, it's free and open source (GPL-3.0). Everything is on this page, with the GitHub link and the install steps:

https://mickaelmancini.com/mini-monitor/en/

Windows for now, Python 3.11, and you need to have logged in to Claude Code once. It reads the same numbers as the usage page, using the login Claude Code already has.

Happy to answer questions!

I work alone on a handful of projects (a website, a book, an e-commerce agent stack), and for a while every Claude Code session started the same way. I explained how the server restarts, which port the CMS is on, that blog posts have to stay drafts. Next day, same thing again.

What fixed most of it was Claude Code's own memory directory. When something goes wrong, the lesson becomes a short rule file plus one line in MEMORY.md, and MEMORY.md is loaded when a session starts (the first 200 lines or 25 KB). A few lines from mine, translated because half of it is German:

- App server: restart with pm2 delete + start. pm2 reload does not pick up new code. - CMS runs on port 1338. Has to match in every config that mentions it. - Blog posts go into the CMS as drafts. Never publish automatically. - docker build does not restart the running container.

I'm at 182 of these now. Anything longer, like project history, architecture notes or notes on clients, lives in a Logseq wiki with about 200 pages. Claude reads the 3 to 5 pages that match the question, not the whole thing.

Two things I learned the hard way:

1. Rules go stale. A rule that says where a config lives is wrong the day you move the config. So every rule that describes how something behaves has a date, and after 90 days Claude checks it against the project (read only) and I decide if it stays.
2. Subagents don't get MEMORY.md. The docs say the main conversation's auto memory isn't loaded into a subagent. If a subagent needs one of your rules, it has to be in the task you hand it, or you give the agent its own memory with the memory: field.

Also, a rule in memory is a suggestion, and Claude can still miss it. Where a mistake would be expensive, I moved it into the deploy script instead. It refuses to run if there are uncommitted changes.

How are you handling this? Just CLAUDE.md, auto memory, something else?

I'm the author of llm-wiki, the open-source (MIT) skill that runs the wiki part and the 90-day check. I wrote up an ordinary working day with it here: https://mehmetgoekce.substack.com/p/i-work-alone-with-claude-code-this

Hi ,

80% of this tutorial is made by Opus. I like the end result, but not easy to have exactly what you want.

I have a lean and formal methods heavy repo, that i need some review and validation, which one is better? the ultra-review or max with fable?

ultra-review still mythos underneath it?

Been using it daily for work and it’s quietly become my daily driver. A few things that won me over:

1. Projects. I know a lot of people hate this feature. I love it. Each project feels like having one personal assistant that only knows that codebase. It remembers the context, it’s easy to navigate, and I can always go back and see exactly what we did. Way better than digging through a pile of random threads.

2. It shows me its work. I’m still pretty new to AI coding and I don’t fully trust it yet. Every change, I want to verify myself. What changed things for me is that I can just ask it to demo what it built. It opens a browser, clicks through, and tests the thing right in front of me. Yes you can do this from the terminal too, but then you’re copying URLs around and testing everything yourself. Watching it prove its own work gave me a lot more confidence.

3. It covers basically my whole workflow now. The only thing I still reach for outside Claude is Grok bot, because I want a general purpose agent for random everyday stuff. Hoping Claude will release something similar in the near future. So I don't have to keep two subscription.

Question: What's your AI stack and daily driver? Any good recommendation for Grok Bot replacement? I feel like it's still the best personal agent out there

Does someone else got access to mythos?

just trying to figure out what the difference against fable, and why had I received an access, lol

i've been using claude code for almost a year now, and wanted to understand what actually happens behind the scenes when you give it a prompt.

so i built this interactive website that breaks down how claude code works internally, from processing your prompt to using tools and generating a response.

the idea was to make it easier to understand what's going on under the hood instead of treating the whole thing like a black box.

check it out: https://inside-claude-code.vercel.app/

I’ve worked at a government agency for about four years. I started as a frontend developer, but now I handle frontend, mobile, and backend development for an ERP system used by around 1,000 employees.

The hardest part is dealing with changing business rules. We have no business analyst or tester, so I have to take on several roles.

Before using AI, I planned my work and wrote code by hand. The pace was slower, but I still had energy after work. Now I finish tasks faster, but I feel exhausted. I drink twice as much coffee, and my skin has gotten worse.

My current workflow is to ask AI for a plan, quickly review it, generate code, test manually, and then ask it to write automated tests. While it’s generating, I switch tabs to check another task and keep prompting. I rarely review the code carefully.

I meet deadlines, but the results feel average, and I’m less confident in my work. I feel like I’m losing control of my own code.

How do you use the time while AI is generating? Does anyone else feel this way?

Claude Code started doing this the other day and I'm not a fan. Maybe I'm just missing something but it gives multiple options to select but never explains what those options mean. I like that it's not being as verbose but this is a bit overkill.
Is there a way to disable this? Or do I need to prompt it away?

​

I’ve been building a complex app with Claude Code for 8 months. Before mid-September, with the extra 50% usage and surprise mid week resets, I took usage limits for granted. Opus Extra/Max did almost everything.

Then the limits changed, and I was running out of usage in 2 days.

So I changed my workflow:

1. Graft Graph

https://github.com/trailhq/Trail-Code

In my experience, it saves roughly 30–40% of usage spent on code discovery in relevant sessions.

1. Opus plans, Sonnet executes

I use Opus 5.5 Medium in plan mode as the orchestrator. After I approve the plan, Sonnet 5.5 subagents handle implementation. No more using Opus for every task.

1. Reduced context from 1M to 400K tokens

A smaller orchestrator context, with subagents handling implementation in their own contexts, means less unnecessary context overhead.

1. Documentation + session handoffs

I make the sessions maintain accurate ".md" files and require Opus to generate a detailed continuation prompt after each planned session. The next session knows what’s done, what remains, and what to do next. Better continuity, less wasted usage, and more structured prompts.

The result: Comparable quality and quantity of work per session, and I now exhaust my weekly allowance just hours before reset.

The lesson? Optimise your workflow, instead of complaining about reduced limits.

Claude Code power users: what’s your setup? How are you managing usage limits without sacrificing code quality? Is there a better Opus/Sonnet workflow I should try?

Is there any sort of command or way to continue a session as right now i just type continue in chat, and that way it sometimes remakes all subagents after checking all the progress which takes some time surely there's a better way to just continue a session that has been stopped by pressing esc or resumed.

So this is the launch video for Reely, the Mac app I've been working on since June. Claude Code made it with Reely from one main prompt, then I did a few fixes in the editor: some animation curves and a bit of text. About 30 min total.
The idea is Claude never writes video code. It writes a json file (scenes, text, 3D phones, keyframes), Reely renders it locally and opens it in an editor where you can still change stuff by hand.

Prompt was roughly this (the video is one of Apple's):
"/reely I want you to recreate this video https://www.youtube.com/watch?v=3uAIqqg8ZHo and adapt text and features from <path to my app>. Keep the pacing and the big kinetic type, one or two words per cut, timed to the beats of the original. The text should sell Reely: it makes a launch video from a screenshot, a screen recording or the app's code, has native text animations and real 3D phones, exports up to 4K and renders locally on the Mac. Show a prompt being typed so people get that an agent is doing the work. Use my app recordings on the phones, mix single phones with a few three-phone shots, and end with a card saying this film was made with Reely, then the logo and getreely.co."

It came back with 43 scenes in 57s.

Biggest thing for me was letting it look at its own frames. It renders a single frame to png, sees the title is cut off or the phone is covering the text, and fixes the json before doing the full render. Before that it was basically guessing.

It's a paid Mac app, iOS apps only. Link in comments