podfeetI'm just curious about something. To those of you who are using vibe coding to either enhance applications and software you've already written or to write entirely new things, are you also adding to your prompt to make what you write accessible?
André Polykanine@podfeet I'm not a vibe coder per se, because I'm a software developer using AI as assisting tool (and yes, I recheck every line of code usually, except for tests, and I don't let Claude to commit, because I prefer to take responsibility of my code, even assisted). That said, yes, I always tell Claude to build anything accessibility-first and check for both visual appeal and accessibility. If needed, I steer the AI in correct direction, but again, I don't vibe code per se.
Erik “Lacraia” Magnusson@menelion @podfeet Letting whatever model I’m currently using do the commiting is the only thing I completely trust it do without any checks. It’s something like ”Create a new git branch, commit with conventional commit message, push to origin, create a merge request with the returning url and open the merge request in my browser.” Even if it screws up this, what’s the harm? In all other regards we seem to treat it the same.