What this repository is: A bilingual, maintainer-curated reference for vibe coding and AI app builders that ship browser-based websites and web apps—default React / Vite / Next.js stacks by product, plus a structured guide to export Lovable to Next.js, SEO, and dual-Git-repository workflows. Sources are vendor docs and reputable public write-ups; your exported package.json is always the technical source of truth.
By @kostja94 · Bilingual 简体中文 · Pair with marketing-skills for agent-ready SEO playbooks · [email protected]
- Who this is for
- What’s included
- Quick navigation
- Document naming
- FAQ
- Scope, limits, freshness
- Related projects
| If you… | Why open this repo |
|---|---|
| Choose or compare Lovable, v0, Bolt, Replit Agent, Base44, or similar builders | Want a single table of declared vs export-time stacks (React, Vite, Next.js, Tailwind, shadcn/ui, etc.). |
| Run SSR / SEO / social previews against a Lovable-linked Vite SPA | Need paths: stay on SPA, prerender/CDN, or migrate to Next.js plus dual-repo safety with Vercel. |
| Maintain marketing or product sites alongside AI-generated codebases | Want cross-links to reusable technical SEO + page guidance (below). |
| Document | Topics |
|---|---|
| Product frontend stack reference (EN) | International and regional builders, browser-only scope, citations to official FAQs and docs—Next.js, React, Vite, Tailwind, Framer, Firebase Studio, CloudBase AI, etc. |
| Migrate Lovable to Next.js — migration & SEO (EN) | Repo A vs Repo B, App Router, Metadata API, checklists; references only official Lovable and Next.js URLs (no third-party tools or paid migrators). |
| Same two guides in 中文 | Mirrors under docs/zh/ (产品前端技术栈, 迁移至 Next.js). |
| Goal | English | 中文 |
|---|---|---|
| Stack comparison across AI builders | vibe-coding-product-frontend-stack.md | Vibe-Coding产品前端技术栈.md |
| Lovable → Next.js, SEO & dual repo | convert-lovable-to-nextjs.md | 迁移Lovable至Nextjs.md |
English Markdown under docs/en/ uses kebab-case with hyphens between words (e.g. convert-lovable-to-nextjs.md) so GitHub blob URLs stay human-readable and predictable across agents and bookmarks. Chinese sources live under docs/zh/ with UTF-8 filenames; pairing is by topic, not literal transliteration.
Full spec: docs/meta/document-naming.md.
Here it means using conversational / agentic tools to generate and iterate web frontends (and adjacent full-stack glue) aimed at products you open in a browser. This repo does not focus on native iOS/Android or mini-program-first stacks (those are labeled out-of-scope where relevant).
No. It summarizes and links authoritative sources. When a vendor silently changes starters, package.json and configs win—treat tables as orientation, not warranties.
Use marketing-skills (160+ Markdown skills): seo-strategy, title-tag, meta-description, schema-markup, landing-page-generator, github, and more—install via npx skills add kostja94/marketing-skills.
Chinese and English mirror the same structure where possible so you can diff or paste into agents. Heading-level anchors may differ slightly with localization.
- In scope: SSG / SPA / SSR web and PWA-facing web delivery paths where stacks are documented or inferred from credible public material.
- Out of scope (by design): Deep backend-per-vendor internals, unofficial migration SaaS catalogs, closed prerender vendor pitches (the Next.js migration doc follows that policy internally).
- Last curated: see each markdown header (
整理日期/ “Last curated”); PRs/Issues welcome when upstream templates change.
| Repo | Role |
|---|---|
| marketing-skills | Agent-oriented SEO, content, pages, GEO, GitHub-parasite skills—pairs well after you pick Next vs Vite. |
Contact: Questions, corrections, or new tooling that pairs with this reference? Email.
MIT License — see LICENSE. Facts can change quickly; cite vendor docs when it matters.
If this repo saved you research time, a star helps others discover it—thank you.