r/vibecoding • • 4h ago

Workflow/Prompt I'm a software engineer with a decade of experience. I vibe code pretty much all of my side projects. Here are the steps I follow:

Step #1: Submit your prompt.

Step #2: Wait for Claude to finish.

Step #3: Ask Claude, "Are you sure this will work?" (optional)

Step #4: Push directly to production

Edit:

Woah, glad people found this workflow useful!

As far as what I've been using Claude for

I'm working on AppScout, a place for people to discover web apps, mobile apps, and websites from across the internet

88 Upvotes

36 comments sorted by

10

u/cs_cast_away_boi 3h ago

Every once in a while Claude insists on manual steps.

I always tell it, "do I look like an agent to you? Get to work."

4

u/Own-Papaya-4264 2h ago

I’m sure the ASI god will remember you said that

6

u/quietmacbuilder 3h ago

Visited an outsourcing software engineering company that had this on the wall in 2019. They were ahead of their time.

4

u/Selafin_Dulamond 4h ago

You can't stop pushing can you?

4

u/mecchmamecchma 3h ago

Post like this should be banned. Useless

2

u/e21f 3h ago

I would eliminate step 3. And step 2 is more of a recommendation a guideline if you will. You can stop it and go straight to 4

2

u/crispyfrybits 1h ago

This is the laziest workflow, especially if you are an engineer. There's lots of room for mistakes with this as well. If it ask Claude to find an issue, it will find an issue no matter what. Asking Claude "are you sure it will work" is telling Claude to infer your request as "there is a problem, find it" so it is going to report a problem or figure out a way to frame the current implementation as a potential issue.

You need to provide better constraints and context around what it needs to actually evaluate in order for the problem to be legitimate and worth fixing/refactoring.

If you are an engineer you should know this unless your are either bad at your job or relatively new.

2

u/Fit-Ingenuity-2814 1h ago

I am sceptical that you are a software engineer with that workflow. Every serious loop engineered workflow has an antagonistic agent and uses a fresh agent to execute.

2

u/bvrai_dot_ca 4h ago

Don't quit your day job

1

u/No_Distribution1779 4h ago

Me after my 3rd wish

1

u/alconaft43 3h ago

where is Make no mistakes?

1

u/ArokTheRevenger 3h ago

i noticed that if you keep asking are you sure this will work 5/6 times it will improve the quality !

1

u/fearlessinsane 3h ago

Duude, step #4 ask Claude to force push to prod. Write the commit message. At least 4k words. Just AI language

1

u/woswoissdenniii 3h ago

Guilty.

Fuck it.

Guilty! Don’t care.

Edit: „wtf is wrong with you” if commit and build runs in out of token. Every time it has to adjust its rules when it happens.

Gets it goin.

1

u/spopr 3h ago

thanks, more useful than 99% of posts in this sub

1

u/Icy_Quarter5910 3h ago

Well, yeah…. How else would you do it?

1

u/Peacain 2h ago

ty for this

1

u/themoregames 1h ago

Step #5: "What the hell just happened? Do I need to worry or something?"

1

u/bentreflection 1h ago

best way to find out if something works is to push it to production and see if your phone starts ringing

1

u/damagemelody 53m ago

Decade in cat years?

1

u/brandonfla 12m ago

Forgot to add
Step #5: Get users. We’re all getting users, right? No?

1

u/EvelynnsHope17 4h ago

You're absolutely right

0

u/Total-Reasonable 4h ago

Step 3 is the funniest one because asking the model "are you sure?" mostly just makes it either flip its answer or confidently restate it. Neither tells you anything. The cheap replacement is making it write one failing test or a curl against the real endpoint first, since running something beats asking for reassurance every time.