do you feel like you reached a point where you let it do its thing alone and the outcome is pretty okay?

I am still working on that. There needs to be still a lot of manual reviews and intervention.

Sometimes it just "starts to cheat" the tests it has written and e.g. hardcodes product ids

I think it even offers a wider range of solutions as before. Things that were very fast but cumbersome to maintain are currently possible.

E.g. super fast, simple code, that is hard to maintain.
Tests with lots of data, where the fixtures are hard to generate.

Now its possible

Yes, it was hard work to get there. And it's nothing like you imagined vibe-coding.

I iterated my CLAUDE.md and Skills for months, learned, read. Definitely not something easy.
But imho totally worth it.

Looking forward into the future with this.

Hard to tell what you want to accomplilsh. What do you mean by dynamically added classes?

Yeah, but you see the problem right?

When you add 8 entities, how much code do you need to get this done? (in Laravel)

I still have troubles to teach Claude to write useful phpunit tests.
I have to hand hold a lot there.

oh you store it in an entity. Well not sure than how to do this with laravel. But would prefer to not write a Cast*Thing for every object I want to embed in an object.

for your example with valinor - all you need is the class Address, and you can spare to write the Caster and whatnot

Store as json, map to objects:

valinor.cuyz.io/latest/getti...

I'd be interested in the line in your CLAUDE.md that made

a) Claude to not write useless inline comments:

// writing content to a file
file.write(content)

b) Let Claude not say: "Oh! You're right"

I tried.. I failed.. here i am :)

Took me a long time to learn this.

But actually.. projections aren't so scary at all. Just update it everytime you write (keep it simple first)

E.g. i just write mapped-to-json DTOs to redis as a projection. And update few other structures in redis for my queries.

It doesnt need to be fancy

therefore it returns everything (at least what I tested).

Solution, you have to use operator "in", www.storyblok.com/docs/api/con...

which would use exact match, and can have comma seperated values, but yeah.

Everyone fell for it when doing this without looking closely at the docs :)

thats the endpoint: www.storyblok.com/docs/api/con...

this is how to query:
www.storyblok.com/docs/api/con...

you can see that operator "is" does not compare, its for checking agains special values.
unfortunately the request does not error when the value from is, is not one of the keywords