What do you think?

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.

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.

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?

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 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?

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?

Skills are great, but finding them isn’t: they’re spread across skills.sh, claude-plugins.dev, Smithery and thousands of GitHub repos, and you mostly install them blind.

So I built skills-atlas, an open-source CLI that merges those sources into one catalog (~75k skills, refreshed every other day) and sorts it into 20 themes.

What it does:

• Browse by theme in a collapsible terminal tree, or skills-atlas ui for a local web page. Search, sort by installs, filter official (vendor-published) skills.
• Read before you install: press p to preview a skill’s SKILL.md. A skill runs with your agent’s permissions, so this felt important.
• Tick several, install once: it runs Vercel’s npx skills add under the hood, to Claude Code, Codex, Cursor or any of 79 agents, per project or globally.
• Knows what you have: installed skills start ticked (untick to uninstall), and outdated ones are flagged; press u to update.
• Export/import your selection to set up another machine.
• Use it from Claude itself: there’s a skill, an MCP server (skills-atlas mcp) and a Claude Code plugin, so you can just ask « find me a skill for Mermaid diagrams and install it ».

There’s a read-only web demo to try it without installing anything: https://devohmycode.github.io/skills-atlas/demo/

It’s MIT licensed, works offline with a bundled catalog, and has no account or server.

Repo: https://github.com/devohmycode/skills-atlas

I’d love feedback on two things in particular: are the themes useful for how you look for skills, and which skills or repos should be in the curated « Recommended » list?

If you use Claude Code on more than one machine, you probably know this routine. You're two hours into something on the desktop, you need to leave, and the laptop has none of it. So you:

• commit something half-broken as "wip" just to get it across
• push, pull
• start a fresh claude on the laptop and explain everything again

onthego does the move for you. From the project folder:

onthego sync laptop

It sends your staged, unstaged and untracked changes plus this project's recent Claude Code sessions to the other machine over your own SSH. Then on the laptop:

claude --resume <id>

Same conversation. You type "ok, where were we?" and it answers with where you actually were.

What I learned building it

• Claude Code keeps each project's transcripts under ~/.claude/projects/, in a folder named after the absolute project path. So plain copying breaks as soon as the other machine uses a different path, like /Users/me/... on a Mac and /home/me/... on a Linux VPS. onthego remaps those paths and leaves the message content alone.
• That folder name has a fun edge case: past 200 characters it gets truncated and a hash of the full path is appended. Long paths needed their own handling.
• I didn't want to trust unit tests for "resume works", so there's a harness that runs the real claude binary against a fake local model server, moves the transcript to a different home and path, resumes it, and checks that the old messages are in the next request.
• .env and other secret-looking files stay home unless you ask for them (then they travel encrypted). Logins are never copied.
• If both machines changed, it stops instead of merging, and keeps a git backup so onthego undo can roll back.

How Claude Code was used: I built it over the last month with Claude Code and Codex. They wrote most of the Go code and tests, and I spent my time on the design and the edge cases above.

Free, MIT, no account, no server. macOS and Linux. Works with Codex sessions too.

Install instructions (npm, or a checksum-verified curl script) are in the README.

GitHub: https://github.com/peerproblem/onthego
Site: https://peerproblem.github.io/onthego/

Happy to answer questions. And if you've solved this some other way, I'd like to hear it.

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?

Treat me like a newbie to claude so what are the some best ways to manage the context window.

The one ik is delegating subagents for tasks so enlighten me with your ideas and methods.

Also drop some cool Mods you know or you created-

I have a rule for my website design agency: a single build site in a single session. Opus knows about that rule, i was checking for session to see at witch step opus is and i was shocked of what i was seeing.

Opus made a new session and he continued there to build the website. I m not speaking about the subagents.

Such a good improvement, right?

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?

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!

Ci sono differenze davvero così sostanziali fra usare l'app Desktop di Claude Code oppure usare in CLI?

i’m thinking of getting a 2nd max sub. anthropic says multiple accounts are fine, but their support bot said not to use them “to get around product limits.” so if account A hits the limit, can i just keep going on account B, same projects? or is that the thing that gets you banned? i only use official claude code. has anyone been doing this for a while?

Recently wanted to try out Orca and quickly realized the same as with JetBrains Air; do all these tools not support sandboxed (via sbx or similar) Claude Code instances? Is everyone just running Claude Code with bypass permissions on his host? Am I missing something, this seems insane to me?

/plan mode has been a lifesaver.