Scaling a prompt library for Nano Banana Pro

I've been messing around with the new Nano Banana Pro model since it dropped, and I think I've finally figured out why it's so finicky.

It seems like the reasoning engine is almost too strong. It overthinks simple prompts. I found that to get consistent results—especially for things like fisheye perspectives or specific camera f-stops—you have to be incredibly rigid with the syntax. You can't just talk to it like you do with Midjourney.

I realized I was wasting hours re-learning the same lessons every time I started a new project. So I decided to productize my own swipe file.

I built bananaprompts.fun as a static gallery for these "stabilized" prompts.

The goal was pretty simple: creating a resource where the prompts are pre-tested to work with Gemini 3’s specific quirks. For example, getting text to render correctly on a sign in a "futuristic cafe" takes a very specific structure that I’ve documented in the library.

I’m also using this project as a bit of an SEO experiment. I’m trying to see if I can capture long-tail traffic for specific art styles (like "lomo camera aesthetic" or "vine-bone transparency") by giving each prompt its own dedicated page.

I’m looking for feedback on the categorization. Right now I have it mixed between art styles and subject matter. Does that make sense to you guys? Or would you rather browse by "use case" (like assets, backgrounds, characters)?

Also, if you have a prompt style that consistently works for you, let me know. I’m trying to expand the "Typography" section because that seems to be the biggest pain point right now.

Thanks for taking a look.