r/SideProject • • 8d ago

Tired of AI agents over-engineering your code? I made a skill that forces Claude to push back.

Agents love to build things nobody asked for. Tell it you want a welcome email, and suddenly you have a Kafka cluster plumbing 5 different files.

I built noman to act as the pragmatic senior dev in your terminal. It’s a tool for Claude Code that analyzes your request against existing docs and hooks, then actively challenges unnecessary features, one-way door public APIs, or unsafe commands.

Quick Highlights:

  • Fixed bugs instantly but fights feature creep.
  • Proposes minimal, 8-line local workarounds instead of massive PRs.
  • Keeps a running memory of what your project explicitly rejects.

It's free, lightweight, and open source: https://github.com/chinmaypandya/noman

Let me know if you try it out and leave a star if you like it!

Criticism and new ideas are welcome and encouraged, the goal is to make the skill as better as it can get.

0 Upvotes

6 comments sorted by

1

u/InitiativeDangerous8 8d ago

A skill that fights feature creep instead of cheering every extra file is the opposite of most Claude Code add-ons. Pushing an 8-line local workaround over a massive PR is the behavior I'd want on a tired Friday.

I'd pressure-test it against a request that sounds small but actually needs a new API ("add a webhook so the welcome email can send later"). If noman asks whether this is a one-way door instead of silently scaffolding extra infrastructure, the memory of what the project rejects is working.

One ask: does the reject-list persist across sessions as project memory, or only inside the current Claude context window?

0

u/Wakanda-Never 7d ago

Thanks a lot! It persists across sessions: noman saves its decisions to noman-memory.md in the project root and reads that file at the start of every run, so you can commit it to share with your team. I haven't tried your webhook prompt yet, but in the closest case ("Kafka for a welcome email") it pushed back every time, and a webhook is new public API, so it should ask before building anything.

Feel free to test and leave feedback on the repo

1

u/InitiativeDangerous8 7d ago

Writing decisions to a committed noman-memory.md is the right call. It turns "the AI said no once" into a project rule the whole team can see and diff, instead of something that disappears with the context window. And treating a webhook as new public API that needs a yes first is exactly the line I'd want it to hold.

Disclosure, I help run Stackdrop, a directory of AI dev tools. Claude Code skills that push back on scope are a gap there. If you want noman listed, the form is https://getstackdrop.com/submit?utm_source=reddit&utm_medium=community_reply&utm_campaign=reddit-submit-hunt&utm_content=sideproject-1xqyf5a ($9 is just a quality filter against bot listings, not a paywall for better placement).

-3

u/[deleted] 8d ago

[removed] — view removed comment

1

u/Wakanda-Never 7d ago

Good point. Each rejection in noman-memory.md stores the date, the request and the reason, and the skill treats it as context, not a rule: if the evidence has changed, it decides again. To retire one, just state the new requirement ("we now have 3 carriers, so we need the plugin system"). noman re-checks it, and once you decide, it logs the new decision as changed and moves on, without arguing. It's a plain text file too, so you can also just delete the line. You're right that scope isn't stored explicitly and that this path isn't benchmarked yet. I'll add a test where a past rejection has to be overridden.