Non-AI-assets: yup, this is sensible. AI is a signal of being unconcerned about being seen as a cheat, absence is good.

Non-AI-code: forget it, you won't be able to avoid it in your libraries, and you won't write the whole engine from scratch.

It's possible to write a whole modern engine without it, but you won't, you'll spin wheels chasing features and never ship.

This is a very flimsy argument to say a vibe coded one-shot Claude app is equivalent to actually hand-made Django app hosted on a Linux system that runs systemd which used Claude PR reviews.

People don't care about your entire dependency chain, see how little the most valuable FOSS libraries recieve in donations or sponsorships compared to end-user apps. They care about how well put together your own app is, which we know AI use changes for the worst (which some argue is worth it for momentum).

As long as your dependencies aren't outright dysfunctional (see rsync debate), it's concensus to disregard AI use there.

Fair point about game development. I'm definitely looking more towards creative tools (like music production apps) because making a game engine is just a Herculean task. I've found that velocity is good (i.e. one meaningful feature every day or two) in the early stages of building for the web without AI.