r/ClaudeGameDev • • Aug 15 '26

Tips & Tricks my difference between vibe coding and coding with ai

just wanted to share my rules, as someone who was anti-AI, to now using claude while coding my hobby project:

1- never do something you cant do yourself.

i am great at maths, but only on pen and paper. formatting mathematical formulas into single line code blocks irks me. my game uses a bit of formulas and fractions. i let claude translate it, but then attach it myself.

2- begin your writing

with normal code i can already write, but where i will have to touch so many dependencies, i either do it myself once, or i write all the function headers, return types, initialise the variables. so far, i use small script files with deterministic outcomes to have 1 feature going. i comment after the function head exactly what to do and then its as simple as to do it.

3- ask claude questions

for things i struggle in doing myself, new code concepts, or game engine unfamiliarity, i ask it in a session where it doesnt have write-access. it's important to never lose track or ownership of your code by becoming dependent.

4- surprise its memories

a good way to make sure your code isnt turning stale is when you do edits, dont tell claude you did, and it always comes back to report the memory mismatch. this is good. because then it will explain what it thinks is different or what the outcome of it is. this strengthens the memories it has and also you get a reminder on places the edit may affect that werent fixed yet. win-win.

does anyone else have any tips on doing this? im tired of people in my life telling me that i should just "prompt the ai to make the game" and question me for taking 4 months developing with no product done. making the game is 70% of the fun itself.

2 Upvotes

7 comments sorted by

3

u/ClosedButOpen Aug 15 '26

Well, I can relate to this quite a bit.
I am also conflicted about using Claude so much for a multitude of reasons. And I also have a set of rules for my development - but I come from a different background, so in practice, it looks different.

For me, Claude is doing the code because the scope of what I am doing reaches far beyond what I've ever known to write.

However, the rest I am doing myself.

- I write the scripts (not coding scripts), and don't ask Claude's 'opinion', so I can say the story of the game is 100% mine.
- I take care of the art direction & I've made all the graphic design myself.
- I created 90% of the 3D models manually in Blender.
- I created the font I needed from scratch.
- All the voiceover I needed - I recorded it myself.
- Music & basically all the sounds are made by other people & credited.
- Photos/videos used in the app are also actual photos and videos.

I think a lot of this is mental gymnastics to make myself not feel like shit because of using Claude. But at the same time, I agree that creating the game is loads of fun, and I wouldn't want to just prompt everything.
But similarly to you, it's been almost a year, and I am still not quite done...

1

u/Top-Dragonfly-70 Aug 15 '26

oh yes, claude doesnt touch the models, music, text that shows up like dialogue, or music (the game is silent as of now) remember if oyu use AI for generativew things then you have to label it as such too.

1

u/ClosedButOpen Aug 15 '26

Nice! Let's see if this approach gets us anywhere. Lol

4

u/jonnybruno Aug 15 '26

In five years you'll look back at how silly this seems.

2

u/Enjoyooooor Aug 16 '26

Making things overly complicated for no reason

1

u/[deleted] Aug 15 '26

[removed] — view removed comment

1

u/Top-Dragonfly-70 Aug 15 '26

dudette, and yes. not everyone who uses AI was an OG prompt engineer