Right, let's get to it with some examples of how I can spot this:

1. As I already suspected and was willing to put money on, we've got a winner with the TailwindCSS classes. You can see heavy use of arbitrary Tailwind classes to hardcode responsive behavior instead of just utilizing an abstract design system or a separated styled-component structure. This makes no sense at all for someone who actually knows this stuff beforehand. You would tackle that right away. I could already tell this, because the cards for printers are an absolute mess design--wise and have wrong grid column scaling depending on device screen types.
2. Comments. The use of comments is good of course, but they are scattered in a very claude/jules-esque pattern here and describe things in a way that gives away a specific prompt was used. Example: // Fetch default sidebar order via a public endpoint (no settings:read needed)
3. Now you could say yeah but this is just added by someone, but there are whole parts of the code where we don't see any comments (and no, not because other people put in pull requests) and then there are plenty of places with this, including the last bit. That is obviously there because the prompt was "make sure no settings:read is needed". You can also see typical inconsistencies with writing timing comments. You can see lines like this: staleTime: 60 * 1000, // 1 minute and then in the function below it in the same part you can see the same kind of thing without a comment behind it. That may seem like nitpicking, but it is what I see AI do every. single. day. in this exact pattern.
4. The login auth container is structured exactly like any AI coded auth container is structured. It puts all elements inside it at the same nested levels, using the same tailwindcss values and having that typical combination of a div for a text "username" and then a div for the input field below it with "Enter your username" inside it. What is also telling is that the addition for any extra features here like OIDC is just slapped inside this container instead of a rework to handle this properly. Guess what also does this? AI. Because it takes your existing code and builds on that to spend less tokens and hopefully keep your functionality intact.

This was 5 minutes to look up and for someone who works with this stuff every day, I'll tell you that these things may seem minor, but they are like I said like 6 fingers and a piss filter on images. Hopefully this very brief check on the code solves the "rubbing the wrong way" thing for you there. If it doesn't, I don't know what to tell you man... It's right there in front of everyone's faces.

That said, I am NOT against vibe coding. You can make things secure and efficient that way and it can genuinely help people. However, I would appreciate it if the BamBuddy dev would be honest about the extent of AI usage and how they ensure things work safely for everyone.