Plainify just got accepted into the Google for Startups Cloud Program. The credits do one specific thing: they let me add Gemini as a second LLM provider for spec generation, alongside Claude.

Why Add a Second Provider

Plainify has been powered by Claude since day one, and that's not changing. Claude stays. But generating a product spec for AI coding assistants isn't one-size-fits-all. Different LLM providers write differently. They structure sections differently, phrase product requirements differently, and make different assumptions when they fill in the gaps. The PLAIN spec format stays the same either way, but the provider interpreting your inputs shapes the final specification more than you'd expect.

Giving you a choice between Claude and Gemini means you can pick the provider whose output fits how you work, or run the same inputs through both and compare the generated specs side by side.

What's Changing in Plainify

Soon you'll see a provider toggle in Plainify. Claude or Gemini, your call. Both generate a structured PLAIN spec file and a ready-to-use bundle you can drop straight into your AI coding assistant, whether that's Claude Code, Gemini, Codex, Cursor, Bolt, v0, or Lovable. Everything else stays exactly where it is: browser-only, no login, no usage caps, free.

Why Specs Matter for Vibe Coding

If you've used AI app builders, you've seen the problem. Vague prompts produce generic apps that all look the same. A structured spec fixes that. It tells the AI coding assistant what you actually want before a single line of code gets written, which is the whole reason PLAIN and Plainify exist. Adding Gemini just gives you one more way to generate that spec.

On the Roadmap

Gemini support is the first step toward making Plainify properly provider-agnostic. More LLM providers may follow. The goal has always been the same: you bring the product idea, Plainify gives you a spec worth building from, and the provider behind it is your choice, not mine.

Shipping soon.