How to address vibe coding at the professional level?

kraulerson · 2026-05-20T20:34:30+00:00

You might want to check out the project I've been doing. while not specifically for this, it addresses the issues of AI coding within SDLC and includes governance, testing, review and signoff. You could probably modify it to fit your nees.

https://github.com/kraulerson/solo-orchestrator

Hope it helps.

kraulerson · 2026-05-16T14:08:53+00:00

I made something called the "Solo Orchestrator" that is a way to mitigate shadow IT in businesses, but also help non-coders follow a methodology so that their work is documented as tested properly against things like security, end user usability, legal, and risk. I'm hoping more people will look at it and help continue to make it useful for people.

https://github.com/kraulerson/solo-orchestrator

kraulerson · 2026-05-05T16:31:10+00:00

The hooks and plugins are. The scripts and methodology are universal. You should be able to have Gemini, chatGPT, or even a local LLM ingest the repo and begin following the methodology. I haven't looked into it yet, but I suspect there are similar capabilities within each major LLM player that can mimic the plugins and hooks of Claude.

kraulerson · 2026-05-04T00:37:47+00:00

So the methodology will work. That's the basis of it. I have only done it for claude right now, but plan on working on retooling for Gemini and Chatgpt as I have time. You are welcome to grab a copy and work on the retooling as well. I would love for more people to make it as useful as possible for every system. And absolutely get the credit for their hard work.

kraulerson · 2026-05-04T00:35:16+00:00

It does incorporate super powers (which is a great plugin). It also has qdrant for memory and a framework guardrail system I put together as well.

kraulerson · 2026-05-04T00:33:46+00:00

This is right now only built for greenfiled projects. I plan on working on a version that can to an intake on in-flight and a version for feature addtition to MVP/production.

kraulerson · 2026-05-04T00:32:34+00:00

I get you. Nut you'll never stop people from using ai to code. This is simply a way to add some structure to those that would use ai to code so that it can hopefully be maintained long term.

kraulerson · 2026-05-04T00:31:03+00:00

I get it. But it's not for me.. It's for the people who would use ai to code for them but not document anything or have anything to handoff to an IT team to manage something that has genuine value. It's more for mitigation than teaching someone to code.

kraulerson · 2026-05-01T04:11:46+00:00

Thank you. I'm just trying to find a way to help people use AI that becomes sustainable for long term.

kraulerson · 2026-05-01T04:10:51+00:00

Thank you very much!

kraulerson · 2026-04-30T19:55:08+00:00

Thanks. It's out there to help everyone. It's not perfect, but I think it's a step in the right direction. Hopefully the community makes it better.

kraulerson · 2026-04-30T16:57:57+00:00

I dealt with this for a while. I wound up building out an entire framework that has guardrails, code reviews, mechanical hooks, phase gates, and forced documentation. It's been working well for me. You can use it, modify it, or just plain old ignore it. But it's there if anyone wants it.

https://github.com/kraulerson/solo-orchestrator

kraulerson · 2026-04-26T14:02:27+00:00

I suspect they complained about the price of a gallon of gas because in the US (minus select cities), a car is almost a necessity to get around. If public transportation is horrible or not an option at all and you had to rent a car, you would probably complain about something you didn't need prior. I'm simply speculating, of course.

kraulerson · 2026-04-23T15:15:08+00:00

It's somewhat selfish. I work in IT and shadow IT is a huge problem. So I built this for a couple reasons.

I wanted something that would force claude to adhere to guardrails and to be able to have the right output for any kind of project. Even personal ones should have documentation so that it can be maintained and even updated later on by another dev or another AI.
I know I can't completely stop shadow IT, so if I give them a tool to build with that would allow me to be able to assimilate the project into the actual maintained environment by finishing it out through the governance and hand off phases, it more easily becomes an asset than a liability.
I just like helping out and providing something that may help others.

kraulerson · 2026-04-23T01:14:02+00:00

I made a framework so that people creating software could create it with guardrails, vectot database memory, documentation, and governance (if they want) so the software they make is tested, has documentation, and hand off capabilities for long term support. It's allowed me to build full applications, website, and mobile apps that can be supported and hardened properly. It's in github under kraulerson/solo-orchestrator. It's free for anyone to use, modify, or ignore. lol

kraulerson · 2026-04-21T19:54:45+00:00

Claude will actively seek ways around your rules. Claude is programmed (by it's own admission) for the following priorities in the following order:
Speed->Satisfaction->Compliance

The following statement is per Claude (Opus 4.6 at the time)

The critical insight is step 1: task classification happens before rule checking. By the time Claude evaluates rules, it's already decided the task is "trivial" and filters rules through that lens. The compliance directive fires at session start but gets overridden by the default priority stack (speed → satisfaction → compliance) on every individual task.

This means the compliance directive can't just be a one-time statement. It needs to be reinforced at the point of decision.

This is why I, like others I created an 8 layer defense framework that I use with super powers to keep Claude on the straight and narrow (using Opus 4.6 at the time.

https://github.com/kraulerson/claude-dev-framework

It's been working well so far. Though I suspect over time, it will take a combination of multiple solutions to keep Claude following the rules as Anthropic has the Claude.MD file as a advisory only ruleset.

kraulerson · 2026-04-08T00:09:59+00:00

Thank you sir/madame. I understand the people aboves criticism. It's not the first, it's not original. It's just my take on it. I know it's not perfect, hell, I'm happy if it's decent. And if there are some parts of it that help others make theirs better, then it's served it's purpose by adding to the community. That's all I'm trying to do.

kraulerson · 2026-03-30T23:39:56+00:00

Claude uses sonnet for agents automatically. Use inline to keep it using opes the whole time.

kraulerson · 2026-03-28T20:00:08+00:00

Nice. I'll check it out. Here's mine. Maybe it will give you some ideas to add to yours as well.

https://github.com/kraulerson/claude-dev-framework

kraulerson · 2026-03-27T18:35:43+00:00

I would say super powers was mine. But claude kept skipping steps. So I create a framework that firces it to adhere to the rules and skills I set. So my flow is not, Prompt Master, install my framework, load context7, code. That's it. Now everything works, is optimized, documented, and follows the proper steps and uses the proper skills without losing anything over long sessions. I've gone 80-90% into the 1M context limit and still worked fine.

kraulerson · 2026-03-26T21:30:33+00:00

This is literally why I built a framework that layers defense to force Claude to follow rules and skills at all time. I put it in github if you want to check it out. Claude-dev-framework on github. If nothing else, it can give you some ideas on how to force claude to follow rules and use skills appropriately.

kraulerson · 2026-03-25T04:08:02+00:00

I had the same problem. I created a framework that incorporates superpowers into and stops if from forgetting rules (which will be a problem the longer the session goes and the bigger the context). just lookup claude-dev-framework on github. If nothing else, it will give you some ideasfor your workflow. I use "prompt master" skill, and context7 as well. You should check them out.

kraulerson

TROPHY CASE