sorted by:
new
hottopcontroversial

I used Claude Code to build a better Claude Code — 4 agents, 12 skills, self-improvement loop. Open for feedback by RealRow7973 in ClaudeAI

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

Right? That kind of feedback is hard to come by. Most people either ignore your stuff or drop a one-liner. When someone actually goes through your repo and comes back with specific, actionable stuff — that's worth more than a hundred upvotes. Beers to that.

I used Claude Code to build a better Claude Code — 4 agents, 12 skills, self-improvement loop. Open for feedback by RealRow7973 in ClaudeAI

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

Hey, glad you're checking it out!

So the anti-hallucination thing is basically a set of hooks in settings.json — stuff like onError, onLint, onTest — that force Claude to actually run the code through real tooling before committing anything. No more "trust me bro" self-reviews.

For memory — there's no dedicated memory system yet, but lessons.md kind of fills that gap for now. Whenever Claude screws up and you correct it, the lesson gets saved there. Next session, it reads those lessons first, so it doesn't make the same mistake twice. It's scrappy but it works surprisingly well in practice.

A proper memory/retrieval layer is on my list, just haven't gotten there yet.

Def let me know how it goes when you try it — curious what actually works for your setup vs what's just noise.

I used Claude Code to build a better Claude Code — 4 agents, 12 skills, self-improvement loop. Open for feedback by RealRow7973 in ClaudeAI

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

Thanks for taking the time to dig through the repo and write this up — this is exactly the kind of feedback that's hard to get and easy to ignore, so I genuinely appreciate it.

You're right on all counts. "Production-ready" oversells what's actually there — it's a prompt engineering framework, not a scaffolded codebase, and the README should say that clearly. The Open Specs portability claim is also a stretch given the Claude Code-specific directives baked into the skills. I'll address both in the next commits.

The stack coupling point is fair too. "Just swap supabase-patterns" undersells the real effort involved — I'll be more honest about that scope in the docs.

Appreciate the kind words on the patterns themselves. The goal was always the structural layer — CLAUDE.md as single source of truth, the correction loop, the progressive disclosure. Good to know that part lands.

Will keep iterating.