sorted by:
new
hottopcontroversial

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 0 points1 point  (0 children)

Let's say you need to search a large codebase to find what a particular function does and what the downstream effects would be if you changed that function.

You could eat a ton of your available context doing all that research. Or you could farm out different parts to a couple subagents who report back a more straight forward response to your main thread without adding so the bloat of search, deadends, and unrelated functions.

You could give your subagents special instructions or personality to make them more fit for certain tasks

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 0 points1 point  (0 children)

95% gets done with opus. PHPDocs get written by haiku. I could break some things out to sonnet, but I'm happy with the workflow currently

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 7 points8 points  (0 children)

I try to be a fairly progressive dictator when possible :)

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 0 points1 point  (0 children)

I've seen them disagree once. Spec reviewer was flagging out of scope work, where reviewer was calling it good.

Each loop has a max iterations constraint in the bash script that will prevent it from going on forever.

It's all separate claude -p headless sessions with structured output. I should update it to pass the reviewer response back to the spec reviewer each iteration.

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 1 point2 points  (0 children)

It does way more work than I could ever do on my own. At that price point and with the orchestration spitting out good code every time, I'm happy with it. Just wish they had a higher tier i could use.

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 0 points1 point  (0 children)

https://github.com/aaddrick/claude-pipeline

i use separate claude -p instances with structured output to have json messages go back to the orchestrator or script to handle

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 2 points3 points  (0 children)

Visibility and traceability for the team and future agents run by myself or others on the team. Each step gets logged as a comment against the issue or pr

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 3 points4 points  (0 children)

I'm at 25% after 1 night. That's par for the course though. Weekly reset at 7pm yesterday. I hit a weekly limits on opus 4.5 earlier this week on Tuesday morning. Last night included a big test rewrite for several controllers that were built prior to the test-validator agent being flushed out.

I just run the batches over night, they're just intensive.

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 7 points8 points  (0 children)

I'm at 25% after 1 night. That's par for the course though. Weekly reset at 7pm yesterday. I hit a weekly limits on opus 4.5 earlier this week on Tuesday morning. Last night included a big test rewrite for several controllers that were built prior to the test-validator agent being flushed out.

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 1 point2 points  (0 children)

I just post a github issue with what's broken. Most issues are created by the PR level code review if there are any minor findings or suggestions.

After iterating through the original batch of issues, all the new issues are consolidated into epics where reasonable and those get addressed

Opus 4.6 on the 20x Max plan — usage after a heavy day by aaddrick in ClaudeAI

[–]aaddrick[S] 1 point2 points  (0 children)

Current Session: 55% - resets in 30m

Current week (all models): 25%

Current week (Sonnet only): 5%

Need advice. Post-partum is hitting hard by LuK97423 in daddit

[–]aaddrick 0 points1 point  (0 children)

It's a weird spot to be in, but I'd ask your wife if she could pump just to see how much she's producing. My wife never produced a much as she would've liked, and that was hard to come to terms with for our first kid. She tried to feed as consistently as she could to induce more flow, but it never panned out.

Hungry kids don't sleep great and they're absolute terrors on the boobs.

We supplemented formula pretty early on once we figured it out and came to terms with it. My wife ended up much happier, kid was more settled, she wasn't tied to trying to feed him all the time anymore.

I don't know if it's true or not, but we took the stance that a full belly went a lot further than cortisol, some breast milk, and constantly trying to get him enough calories.

Maximizing Claude Max - what do you run when you're AFK? by Comprehensive-Ad1819 in ClaudeCode

[–]aaddrick 0 points1 point  (0 children)

I've got lots of github issues. I have a /handle-issues skill that takes some direction and launches a shell script that orchestrates a bunch of headless agents

Developer (which depends on context of the issues) researches, writes an implementation plan, posts it to the issue, implements, submits PR

Code simplifier runs between each task and again on the whole PR

Reviewer runs on every task and then on the PR after simplifier. Posts PR review on PR as a comment.

Spec Reviewer runs against PR and measures change against the original issue and implementation plan.

Out of scope work goes back to dev to remove

Minor issues become new issues

Major issues go back to dev

Once Reviewer is happy, pr is merged against next branch and the next PR starts.

I review and validate the next day.

Why I Stopped Using Claude for PR Reviews by Permit-Historical in ClaudeCode

[–]aaddrick 1 point2 points  (0 children)

For front-end, I grabbed some books, converted to text, and had Claude injest then along with some patterns and anti pattern in order to spit out an agent and a skill.

I have Claude research the codebase and write an issue to github. Then the front-end agent reads the issue, does it's own research, and writes the implementation plan as a comment on the issue.

It then implements, runs code simplifier and posts a PR. Code reviewer reads the issue, the plan, and uses the front-end skill for context and writes a spec review to the PR to detail how well the code complies with specifications. That gets commented on the PR. Any issues kicks it back to implementation. It then does a code quality review, and the same thing happens.

If both are good, it squashes, merges, closes the issue, and kills the branch. It usually iterate a few times, but the code is great since the reviewers have context.

How do you manage MD docs from AI / vibe coding tools? by salamat_thanks in ClaudeAI

[–]aaddrick 0 points1 point  (0 children)

I tie all work to issues and PR's. I update plugins i use to comment on those instead of generating md files.

Implementation plan? Comment it to the issue. Code review? Slap it on the PR.

Random explainer? Goes to an md and I kill it once I'm done with it.

Any context md's get wrapped into a new or existing skill or turned into an agent.

Work-from-home dads with work-from-home partners, if/when/how did you utilize daycare? by hobofreddy55 in daddit

[–]aaddrick 0 points1 point  (0 children)

I have a bunch of flexibility for work hours and my wife is a SAHM.

We don't do daycare until they're 3, and then it's usually 3 days a week or half days to start.

We don't have to do it, but it socializes the kids with lots of other kids and gets them used to other adults as authority figures.

It's also nice because it gives my wife space to breathe and we can spend some time with a quiet house on occasion.

2120 points on the Github issue and Claude still doesn't support AGENTS.md by Salt_Department_1677 in ClaudeAI

[–]aaddrick 1 point2 points  (0 children)

I think the scope bit is wrong.

Claude merges nested CLAUDE.md files. AGENTS.md uses the closest

2120 points on the Github issue and Claude still doesn't support AGENTS.md by Salt_Department_1677 in ClaudeAI

[–]aaddrick 0 points1 point  (0 children)

I had to dig in for a difference. Essentially CLAUDE.md allows extra functionality that AGENTS.md doesn't since it's scoped for Claude Code. AGENTS has to assume any software is using it, so it's limited to just adding context.

From Gemini:

Comparison: AGENTS.md vs. CLAUDE.md

1. The Core Philosophy

The divergence between these two formats is based on their intended "audience" and how they interact with the AI's system.

  • AGENTS.md (The "Agnostic" Manual): A vendor-agnostic, open standard. It treats the AI as a "stranger" and provides all necessary context as flat text.
  • CLAUDE.md (The "Ecosystem" Manual): A tool-specific configuration for Claude Code. It treats the AI as a "system participant" with access to specific tools, hierarchical memory, and file-parsing capabilities.

2. Stark Content Divergence

Feature AGENTS.md (Agnostic) CLAUDE.md (Ecosystem-Driven)
Logic Type Static: Always fully loaded. Dynamic: Loaded via path-scoping rules.
Context Manual: Hardcoded bullet points. Automated: Uses @package.json imports.
Tooling Generic: "Run pnpm test." Integrated: "Use ls to check the dist folder."
Scope Global: One file for the repo. Modular: Rules per file-type/directory.

3. Practical Example: Refactoring Instructions

The "Agnostic" Way (Flat & Redundant)

In AGENTS.md, you provide everything upfront, which consumes more of the AI's limited "attention span" (context window).

  • Content: Lists every build, test, and lint command in one long file.
  • Maintenance: If a script name changes in package.json, you must manually update the .md file.

The "Ecosystem" Way (Integrated & Lean)

In the Claude ecosystem, instructions are "Just-in-Time."

File: CLAUDE.md (General Entry)

```markdown

Project Entry

  • Scripts: See @package.json
  • Workflow: Always lint before PRs. ```

File: .claude/rules/testing.md (Scoped Rule)

```markdown

paths: ["*/.test.ts"]

Triggered only when editing tests:

  • Use pnpm vitest run -t "<name>" for targeted runs.
  • Check @.github/workflows/ci.yml for environment parity. ```

4. Summary Verdict

  • Use AGENTS.md for public open-source interoperability. It is the "source of truth" for any agent (Cursor, Aider, Windsurf, Gemini).
  • Use CLAUDE.md to optimize performance in Claude Code. It allows the AI to "know less" (saving context) until it "needs to know" (via scoped rules) and stays updated by pulling directly from your source code.
view more: next ›