Vibe Vibe: A Chinese-Language Vibe Coding Curriculum, Read Before You Adopt It

The Gap Vibe Vibe Is Trying To Fill

The README states the problem plainly: Vibe Coding has become a global trend, with more startup code written with AI assistance, but Chinese-language learning material is fragmented. What is missing, in the authors' framing, is a single path that starts at zero programming background and ends with a deployed product. That is a curriculum problem, not a tooling problem. Cursor, Windsurf, Bolt.new and Replit already exist, and the beginner track includes a selection guide for them. What did not exist, according to the project, was the sequence of lessons that tells a beginner which of those to open first, what to ask it, and what to do when the generated code breaks. The audience is explicit in the README: people with no programming background, university students, founders, working programmers, and office workers who want to ship ideas with AI. The repository is hosted under the Datawhale organisation, which the README links to for contributor onboarding and project governance.

Four Tracks And What Each One Actually Promises

The curriculum splits into four boards. The beginner board (基础篇) covers why now is a good time to program, the distinction between Vibe Coding and Spec Coding, tool selection, MVP thinking, prompt engineering, a first project built in rounds, debugging with AI, and the limits of the approach. The advanced board (进阶篇) is sixteen chapters organised around a full delivery pipeline: environment setup and package managers, PRD-driven development, build mechanics, UI and UX, environment variables, database persistence, testing, localhost versus public access, Git, serverless deployment and CI/CD, DNS, cloud server operations, SEO and analytics, and user feedback loops. The practice board splits by audience (liberal arts and business students, science and engineering students, office workers) and adds an advanced section covering deployment, databases, user authentication, RAG, vector databases, MCP integration, and SaaS or mobile projects. The fourth board is a curated reading list of company blogs, podcasts, research reports, newsletters and communities. The advanced track names its stack: Next.js 16, React, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM and PostgreSQL. One caveat the README itself carries: the advanced chapters are described as having readable prefaces, which suggests the chapter bodies may not all be published. Verify that before assigning the advanced track as required reading.

How The Tutorial Site Is Built And Served

The primary language listed for the repository is Dockerfile, which tells you what the repository mostly is: a documentation site with a container recipe, not an application framework. The README gives two self-hosting instructions. The repository ships a Dockerfile and a docker-compose.yml, and the documented command is `docker compose up -d --build`. The default address is `http://localhost:1024`. For anything beyond that, the README points to a deployment guide at `docs/deployment/index.md`, which it says covers fuller deployment options, static file hosting, and offline environment considerations. The offline note matters for the intended use case: a classroom or an internal network without reliable outbound access. The README does not document environment variables, build arguments, or image size, so sizing a deployment from the README alone is not possible. The site is also live at www.vibevibe.cn, which is the path most readers will take.

The Online IDE And Skills Are Announced, Not Shipped

The README has a section titled as a preview of an advanced version: an online development environment with a cloud IDE bundling Node.js 24, Python and Docker, more than 50 preinstalled AI Skills covering the development workflow, and a claim that nothing needs to be installed locally. It ends with a wait-and-see line. Treat this as a roadmap item, not a feature. Nothing in the supplied material shows a release, a date, or a repository path for that environment, and the repository has no releases at all. If your reason for adopting Vibe Vibe is the browser-based IDE, you are adopting a promise. The Docker self-hosting path is the only deployment mechanism the README actually documents today.

Where The Curriculum Stops Short

The beginner track's own outline includes a chapter on the boundaries of Vibe Coding (5.5 知边界), which is honest, but the curriculum as a whole is aimed at small personal tools. Chapter 4 builds a personal utility, and the MVP framing in chapter 2 pushes readers toward the smallest thing that runs. That is the right pedagogy for a first project and the wrong preparation for maintaining a codebase someone else will inherit. The advanced track does cover Git, CI/CD and cloud operations, but a reader who stops after the beginner track will have no version control habits, and the README does not say whether the beginner track introduces Git at all. There is also a language boundary: the README is Chinese-first, with an English README.en.md linked at the top, but the tutorial content itself is described in Chinese and the site is www.vibevibe.cn. An English-speaking team cannot adopt this as-is. Finally, the licence is a real constraint, covered below.

What To Read Instead, And Why The Difference Matters

For an English-speaking audience, the most direct alternative is the vendor documentation for the tools the beginner track already recommends: Cursor, Windsurf, Bolt.new and Replit each publish their own onboarding material, and each is written by the team that ships the tool. The difference in approach is structural. Vendor docs are reference material organised around features; Vibe Vibe is organised around a learner's progression, with an explicit MVP-first stance and a debugging chapter on using AI to fix AI output. If you want the reference, take the vendor docs. If you want the sequence, Vibe Vibe is the one that supplies it, provided your readers handle Chinese. For teams already comfortable with the stack, the advanced track's Next.js, Drizzle and PostgreSQL combination overlaps with general full-stack material, and the differentiating part is the framing around PRD-driven development and deployment pitfalls rather than the technology list.

Licence, Maintenance And What To Check Before You Commit

The README's licence section applies CC BY-NC-SA 4.0: attribution, non-commercial use, and share-alike. That rules out repackaging the material into a paid course, and the share-alike term means derivative teaching material carries the same licence. If you are a company wanting to run this as internal training, the non-commercial clause is the line to examine with your own counsel; this article does not give legal advice. The repository is not archived and the last push shown is 2026-04-30, so work is ongoing. There are no releases, which means there is no versioned snapshot to pin a course to; you get whatever main contains. Contributions run through issues and pull requests, with a Datawhale volunteer team referenced for follow-up on unanswered threads. Before adopting, check the licence file in the repository rather than the badge, confirm how much of the sixteen advanced chapters is actually written, and check whether the online IDE preview has become a shipped feature. Those three checks determine whether the curriculum you are planning around exists yet.

Editorial conclusion

Assign it to beginners, university clubs and internal training groups that read Simplified Chinese and want a structured path from idea to deployed product; the README maps four tracks to different starting points, and the Dockerfile lets you host the whole thing on an intranet. Do not adopt it as an English-language resource or as a source of production code, because the README is Chinese-first and the repository is a tutorial site rather than a library. Before committing, verify three things in the repository itself: the actual licence file, whether the sixteen advanced chapters beyond their prefaces have shipped, and whether the online IDE and Skills preview is still a preview.

Official sources

1. datawhalechina/vibe-vibe on GitHub
2. Issues
3. Project website
4. README