Phase 1 public clone

Bilingual prompt pages that turn discovery into image generation

Ship the public clone first, then layer billing, credits, and the real generation backend.

111+

Scene inventory

2

Supported locales

20+

SEO pages

2 credits

Per run cost

Homepage generator preview

2 credits

Studio Product Lighting

Text-to-image / image-to-image modes
Reference upload placeholder
Pricing and credits UI ready
Open generator

Why this shape

Follow the PRD shape: ship what can validate the market first

Public routes, prompt detail pages, mirrored locales, and conversion paths land first. The expensive backend pieces join later.

SEO-first prompt architecture

Dedicated list and detail pages make each prompt indexable, linkable, and measurable.

Localized route parity

English and Chinese paths stay mirrored so content ops and SEO stay predictable.

Phaseable product stack

The public shell is ready first, then billing, credits, uploads, and providers can slot in cleanly.

Featured prompts

Show how prompt discovery connects straight into generator usage

Each card includes detail, copy, and generate actions to mirror the prompt-detail-to-generator flow from the PRD.

Three steps

The rollout sequence is intentionally simple

Validate traffic and conversion with the public clone first, then invest in credits, billing, and the generation backend.

01

Publish prompt pages

Ship landing-ready category pages and detail pages with generator entry points.

02

Convert visitors

Use pricing, prompt copy actions, and a prefilled generator shell to push the next step.

03

Productize the backend

Add auth, credits, payment webhooks, storage, and image generation once the public funnel is validated.

Social proof

What matters is whether the product catches user intent fast

Prompt pages are not passive content pages. They are the middle layer that pushes browsing into copying, generating, and purchasing.

The prompt pages feel like landing pages, not just docs. That made paid traffic far easier to convert.

Maya, Beauty Growth Lead

We need fast white-background variants, social mockups, and reusable prompts. This structure gets us there.

Rico, Marketplace Operator

Bilingual SEO pages plus a generator shell is the right MVP shape for testing demand before expensive backend work.

Lin, Creative Strategist

FAQ

Answer the obvious questions up front

This clarifies what already ships in the public clone and what lands next in the productized backend.

What is implemented in this first slice?

The public marketing site, prompt library, localized routes, pricing shell, blog shell, and generator shell are in place first.

Are credits and real generation live yet?

Not yet. The UI is prepared so billing, ledgers, provider adapters, and uploads can be wired in next.

Why duplicate English and Chinese routes now?

Because SEO and mirrored content are a core product goal, route parity is part of the MVP shape.

Can this move to DB-backed content later?

Yes. The content is already centralized and typed so it can move into Drizzle models and admin flows cleanly.

Ready to build

Next step is wiring auth, credits, and the generation backend