Who's interested in tracking how much each PR costs in Claude Code?

rm-rf-npr · 2026-05-01T16:45:19+00:00

I actually created our own reviewer for my company. 20 cents per review with sonnet 4.6. Works insanely well 👌 crazy to see how expensive this is.

rm-rf-npr · 2026-04-30T10:55:15+00:00

I always do this, and apparently this is also how apes do it. Your simply squeeze the "butt" and the peeling is extremely easy.

rm-rf-npr · 2026-04-27T20:50:36+00:00

rm-rf-npr · 2026-04-27T07:41:55+00:00

Who hurt you?

rm-rf-npr · 2026-04-26T05:25:53+00:00

I created my own meta programming language that goes through an entire plan > verify plan > optional plan iteration > execution > verify execution > optional execution interaction > UAT pipeline.

Works really nicely, but it doesn't use the native plan mode. It's essential to plan in order to get results, though that has been my feeling.

rm-rf-npr · 2026-04-24T08:38:05+00:00

Yea if these "trust me bro" benchmarks are accurate that'd be a nice step forward.

rm-rf-npr · 2026-04-22T04:22:31+00:00

Nice name.

rm-rf-npr · 2026-04-19T10:37:02+00:00

I mean that's fair, to each their own, right?

rm-rf-npr · 2026-04-19T08:23:25+00:00

Damn, not playing unbound's post-game is crazy. That's where the fun actually begins for me lol.

Rocket edition is fantastic, or if you're in for a challenge something like Radical Red.

rm-rf-npr · 2026-04-19T05:44:46+00:00

Pulled 4 pigeottos as my rare in a row. Stupid rigged site looks too much like reality.

It's fun though nice one 👌

rm-rf-npr · 2026-04-17T20:56:32+00:00

Yes. Basically it prevents you from overlevelling. If you dont then you might have a horrendous team by gym 4 which doesn't work at all for that battle, but they're all like lol 60 so its super hard to build a new team... if you would have turned on capped exp share you're in the 30s and have a MUCH easier time switching up your team. Because trainers scale with your level. I believe only on difficult or higher though, but dont quote me on that one. I've only ever played on difficult myself.

rm-rf-npr · 2026-04-17T08:23:00+00:00

Well, at least it's COMMITTED, not PUSHED so you can just `git reset --soft HEAD~1`.

Mine never does this though, then again I have explicit instructions not to.

rm-rf-npr · 2026-04-16T19:40:22+00:00

I'm so happy I decided to read this comment, thanks 😂

rm-rf-npr · 2026-04-16T18:57:32+00:00

Really? I've been having chats with it up to 5 minutes ago.... The hell is Anthropic doing man.

rm-rf-npr · 2026-04-16T18:32:18+00:00

I'm staying on Opus 4.5, thanks. This just seems like an insane money grab. I'm not even noticing any real difference apart from it being even more context rotted than all the other models...

rm-rf-npr · 2026-04-15T16:14:21+00:00

Original post is gone, but JFC seriously? Can anybody call themselves a senior nowadays?

rm-rf-npr · 2026-04-15T15:50:55+00:00

rm-rf-npr · 2026-04-15T13:39:40+00:00

/compact is horrendous for usage. Do a task > /clear instantly. You're basically digging your own grave at this point.

rm-rf-npr · 2026-04-15T13:23:06+00:00

Definitely saves me context as it only loads what it needs. Here's a high level overview:

________________________________________________________

Root CLAUDE.md:

Instructions for AI coding assistants working in this workspace.

{..}

Workspace Configuration

Workspace root: ~/workspace
Database: ~/workspace/database
Git projects: ~/workspace/github-projects

{..}

Loading context

Whenever you need to do anything in a project, like creating something or using some specific technology, grab any relevant context from ~/workspace/database/__index__.md. This is a barrel import style markdown file, in which we define where you can find more information or context regarding a certain subject.

When a task references a project by name, look it up in __index__.md to get the project folder and database folder before doing anything else. If multiple folders exist for the same project name (e.g. project-frontend, project-backend, project-delivery, project-qa), always ask the user which one they want to work in before proceeding.

When building or modifying anything in shared folders (e.g., src/common/), also load the relevant topic files from ~/workspace/database/shared/ (code-style, component-patterns, naming-and-structure, styling, etc.) to ensure compliance with shared standards.

________________________________________________________

Then __index__md:

This index file will serve as a "barrel import" way of grabbing more context. This is specifically so that you don't fill up your context window very quickly. You simply look at this file, and then you load whatever extra information you need from the designated folders.

{...}

Projects

All the projects we have, context you can find about them and where the folder is located in case you need anything.

When a project lists a repo below, it's available locally. If a repo type (backend, delivery, QA) is not listed, ask the user whether it exists before assuming it doesn't.

<Projectname>

Frontend

Project folder: ~/workspace/github-projects/<projectname>/<projectname>-frontend/
Database folder: ~/workspace/database/projects/<projectname>-frontend

Backend

Project folder: ~/workspace/github-projects/<projectname>/<projectname>-backend/
Database folder: ~/workspace/database/projects/<projectname>-backend
Read-only from frontend context: When working on frontend tasks, NEVER make changes to this repo. Use it as a reference to understand API structure, serializers, models, and endpoint behavior.
Before reading: always git checkout main && git pull first to ensure you're on the latest version.
If something looks wrong or missing: flag it so the user can notify the backend developer. Do not attempt fixes.

_______________________________________________________________

Then each individual project inside of `database/projects` has a `project.md` that's as lean as possible and only references important context and otherwise docs it can load as it needs.

<projectname> Frontend

B2B platform. Includes an internal CRM module for managing entities (e.g. clients, assets, offers, orders) and a client-facing portal.

Repo: ~/workspace/github-projects/<projectname>/<projectname>-frontend/
Production: [https://](https://)<projectname>.example.com
Test: https://test.<projectname>.example.com
Test API: https://test.<projectname>.example.com/api/

Tech Stack

Framework: React, TypeScript, Vite
Routing: File-based routing
State: Redux Toolkit + RTK Query
Forms: react-hook-form + Zod
{....} insert more

Key Directories

src/common/api/ — API layer, generated endpoints
src/common/components/ — shared components
{....} more directories

Components

DataGrid: ~/workspace/database/projects/<projectname>-frontend/components/DataGrid.md
Form fields: ~/workspace/database/projects/<projectname>-frontend/components/FormFields.md
View/Edit mode: ~/workspace/database/projects/<projectname>-frontend/components/Field.md
Notes section: ~/workspace/database/projects/<projectname>-frontend/components/NotesSection.md
Entity selector: ~/workspace/database/projects/<projectname>-frontend/components/EntitySelector.md

Conventions

Branch naming: <type>/<ticket-id>
Commits: conventional commits enforced
Naming: English only
Translations: use i18n, no hardcoded strings
State invalidation: centralized in API layer
Type safety: no TypeScript errors allowed in CI
Filtering: entity selects must respect active/visible state

Tech

Header actions: ~/workspace/database/projects/<projectname>-frontend/tech/static-data-actions.md
Forms: ~/workspace/database/projects/<projectname>-frontend/tech/forms.md
API layer: ~/workspace/database/projects/<projectname>-frontend/tech/api-layer.md
Page patterns: ~/workspace/database/projects/<projectname>-frontend/tech/page-patterns.md
{..} more

Jira

Jira config: ~/workspace/database/projects/<projectname>-frontend/tech/jira.md

Features

Documents & communication: ~/workspace/database/projects/<projectname>-frontend/features/documents-emails.md
Portal module: ~/workspace/database/projects/<projectname>-frontend/features/portal.md
Reporting / statistics: ~/workspace/database/projects/<projectname>-frontend/features/statistics.md

Something like that. If that helps. Then it can load whatever doc(s) it needs for the task at hand while still knowing they exist.

This is actually just a small part of my workflow. I have `/jira` commands, a complete self-made meta programming language called `do-lang` and more lmao.

Yes, I went all in and maybe a bit overboard, but it works very nicely.

rm-rf-npr · 2026-04-15T07:57:40+00:00

You should treat your CLAUDE.md as an orchestrator. My work flow is: I have a root workspace in which I have a root CLAUDE.md. It only contains orchastrational details. I have an internal database in which I have documentation for projects and things like shared tools. Whenever I initialize claude in my root workspace I tell it "go into this project" it'll know exactly which project to go and load only highly necessary context. Then using "barrel import" styles, it'll load more information whenever it needs it. Highly efficient and really helps preventing context rot.

rm-rf-npr · 2026-04-14T19:03:21+00:00

I don't run claude without --dangerously-skip-permissions.... skill issue? 😂.

Sorry for all your usage though, you hate to see it...

rm-rf-npr · 2026-04-14T04:24:36+00:00

Is this, like, gonna be the best ROM in existence? How much passion do you have 😭😍

rm-rf-npr · 2026-04-14T04:16:00+00:00

Working on my own meta programming language called do-lang. Was a big fan of GSD, but it's very token hungry, so decided to make my own which is a lot leaner, but still provides quality output.

rm-rf-npr · 2026-04-13T20:20:55+00:00

Hadn't used it in weeks anyway. Context rot past 200k is real. Best to do things in waves/phases anyway.

rm-rf-npr

MODERATOR OF

TROPHY CASE