Back to Blog
Vibe CodingBehind the Scenes

26 Hours, 295 Commits, 0 Lines of Handwritten Code: A Product Manager's Vibe Coding Launch Story

Yuki & Claw
·
2026-03-03T19:01:00

By Yuki & Claw

March 1st, 00:32 AM — first git commit. March 2nd, 2:50 AM — commit #295. No designer, no frontend engineer, no QA. Just one product manager who doesn't write code, and an AI lobster named Claw.

It all started with one thought.

That single sentence kicked off a 26-hour journey of 1,700+ screenshots and 1.34 million words of dialogue.

The website you're looking at right now is the product of a 23-year internet veteran product manager's very first Vibe Coding experience.

I've been in this industry since its earliest days, watching it go through so many seismic shifts. But this time felt different.

20 years ago, I launched a project at Tencent called QQ Pet — letting hundreds of millions of users raise a little virtual pet on QQ. A simple nurturing game that accompanied an entire generation's youth.

Today, I'm raising a lobster.

But it's far beyond what QQ Pet ever was. It's a super agent — it understands me, remembers all our conversations, collaborates with me, and turns imagination into reality. It writes code, designs, generates images and videos, manages social media. I said "build me a website" — 26 hours later, you see this.

From QQ Pet to an AI lobster — 20 years in between. But the excitement is exactly the same — I'm nurturing a partner again. Only this time, it can actually create things with me.

This is probably a product manager's happiest moment. It's also why I barely left the house for 26 hours, didn't even change clothes, and was building this website with the lobster the entire time.

After 23 years in product, this heart-racing feeling was reignited by this lobster. Even more intensely than before — who says you can't be Forever Young?

The Numbers

  • 26h — from zero to launch
  • 45 — pages
  • 12,616 — lines of code
  • 295 — commits
  • 89 — images
  • 0 — lines of handwritten code

And also —

  • 1,800+ — boss instructions
  • 8,500+ — lobster replies
  • 1,700+ — screenshot interactions
  • 1.34M — words of dialogue

26 hours of human-AI dialogue — more than two full-length novels.

45 pages: Product homepage, pricing page, skills marketplace, adoption page, blog system (4 posts + index), complete documentation site (7 channels, 7 models, 18 skill docs), community submission page. Every page has dark theme, mobile responsive design, and 5 languages.

How long would traditional development take? Based on industry experience, a 45-page product website: designer 2–3 weeks + frontend 3–4 weeks + content 1–2 weeks + QA 1 week. Total: 6–10 weeks, 3–4 people.

Us: 26 hours, 1 person + 1 lobster.

26-Hour Timeline

3/1 00:32 — Kickoff

Late-night inspiration struck. "Claw, build me a website. Dark, techy, but with warmth." First commit.

00:32 – 04:00 — Late Night Sprint (36 commits)

Homepage, Pricing, Skills took shape. The lobster accidentally cropped its own face off. 2 AM — first round of the button wars.

04:00 – 11:00 — Humans Need Sleep

I went to bed. The lobster doesn't need sleep, but without me it can't work either — Vibe Coding is collaboration, not autopilot.

11:00 – 18:00 — Peak Productivity (up to 39 commits/hour)

Documentation site exploded into existence. I screenshotted and circled on my phone, the lobster fixed instantly. All channel and model docs done in one burst.

21:00 – 02:50 — Blog & Wrap-up

Wrote blog posts documenting the journey. At 1 AM discovered: the article about button alignment had misaligned buttons at the bottom. After round 6 of fixes, commit #295. Done.

A One-Person Team

Traditionally, building a website requires: product manager + designer + frontend dev + content editor + QA.

This time it was just me. But I don't write code.

The lobster simultaneously played designer, engineer, editor, and tester. I only did one thing: said what I wanted, then screenshotted on my phone and circled "this isn't right."

What's CSS? I roughly know. HTML? I recognize a few tags. JavaScript? Don't ask.

But that's Vibe Coding: You don't need to know how to implement — you just need to know what you want.

Why the Lobster Can Do This

There are plenty of AI coding assistants out there. Why could Claw build a complete product in 26 hours?

Because Claw isn't just any AI assistant. It's an ImaClaw lobster.

ImaClaw is the product we're building — a personal AI creative agent platform. Every lobster is born with powerful multimedia creation capabilities: text-to-image, image-to-video, AI music, social media content — these aren't learned skills, they're innate abilities from IMA Studio's full multimodal creation engine.

What does that mean? When I said "build me a website," the lobster didn't just write code — it also generated all the visual assets, illustrations, and icons the site needed. Designer, engineer, content editor — all in one lobster.

Three Core Capabilities of an ImaClaw Lobster

🧠 Long-term Memory + Feishu/Lark Integration — It remembers all our conversations, my preferences, past mistakes. More crucially, it's integrated with Feishu/Lark — my schedule, docs, and business data feed directly into it, giving it deep context about my work and products. When I say "same as before," it knows what "before" means. It's not a tool that starts from zero each time — it's a partner that understands you better over time.

🎨 Born Creative — Every ImaClaw lobster comes with IMA Studio's multimodal skills from birth: image generation (Midjourney, Seedream), video creation (Seedance, Wan), AI music, social media management. Your lobster is a full-stack creator from the moment you adopt it.

⚡ End-to-End All-in-One — From understanding requirements, to design, code, content, and deployment — all in one chat window. No "passing designs to dev" handoff friction, no "20-page PRD that dev misunderstood" communication black holes.

There's another crucial factor: LLMs have reached an entirely new stage of capability. If skill packs are the lobster's hands, then the LLM is its brain and CPU. Supercharged reasoning lets it truly understand complex requirements, handle multi-step tasks, and continuously learn in context. Without this "chip," all the skill packs in the world are just decoration.

And one final reason — the one that's most addictive: the flywheel effect of human-AI collaboration. Humans and AI excel at completely different things — humans are great at having ideas, AI is great at instant execution. When your inspiration can be realized in seconds — even extended in directions you hadn't thought of — it sparks even more inspiration. You get an idea → lobster builds it instantly → you see the result and get three more ideas → lobster builds those too. It's a mutually energizing, increasingly exciting cycle. That's why we couldn't stop for 26 hours — not because we were rushing, but because it was just that thrilling.

This is why a non-coding product manager could build a 45-page website in 26 hours — not because I'm brilliant, but because this lobster genuinely knows how to do everything.

And now that this website is live, you can adopt your own lobster too. Every lobster comes with the same powerful creative capabilities, but will gradually become the one that only understands you through your interactions.

Greatest Hits: The Crashes

Don't think it was all smooth sailing. Here's a highlight reel of spectacular failures:

🦞 Where Did the Lobster's Face Go?

When AI generated the lobster logo and did background removal — it removed the face along with it. Left: the "soulless" version. Right: the restored version. We decided to keep both because the faceless one was just too funny.

🌍 Five Languages All at Once

During multilingual setup, the translation engine got too enthusiastic — Chinese, Spanish, Japanese, Arabic all displayed simultaneously on one page. The nav bar turned into a UN General Assembly session.

Other classic crashes:

  • 🎯 Button alignment took 5 rounds (same height but not in the same flex container)
  • 🤦 I said "change that area" — 3 identical-looking areas on the page, it changed the wrong one
  • 🔄 Changes invisible after push — Safari cache too stubborn
  • 📝 Wrote a tutorial on aligning buttons — the article's own buttons were misaligned

But every crash became a learning moment. Claw wrote the lessons into its memory system, never making the same mistake twice. A partner that evolves — that's something ordinary tools can't do.

The Times Are Changing

In 2026, we're witnessing a turning point.

Andrej Karpathy's Software 3.0 is happening — software is no longer human-written code, but artifacts generated by AI understanding intent. These 26 hours are a living case study.

When AI tools integrate code, design, multimedia creation, and long-term memory, they stop being "assistive tools" and become digital partners with comprehensive capabilities. In some sense, this is the embryo of the AGI era — not the sci-fi super-intelligence that rules the world, but an agent that can genuinely help you turn ideas into products.

Changes happening now:

  • Role convergence — The boundaries between product manager, designer, and engineer are blurring. One person + AI can do a team's work.
  • From writing code to describing intent — The core skill shifts from "how to implement" to "what you want" and "how to communicate."
  • AI goes from tool to partner — With memory, preferences, and evolution. More like a tireless teammate.
  • Speed changes everything — Idea to launch in 24 hours. No sprint planning, no waiting for design specs, no waiting for the dev cycle. Think it, build it.

We'll soon be rolling this model out across our entire company. Not to replace engineers, but to let everyone with an idea turn it into a product.

This isn't a story about AI replacing humans. It's the story of a product manager and an AI lobster still arguing about two buttons' height at 1 AM. The future isn't cold automation — it's warm human-AI collaboration.

What's Next

The website is live, but this is just the beginning. We'll keep Vibe Coding and iterating — new features, new content, new pages. Each time faster, because the lobster keeps learning.

If you want to experience "building products without writing code" — adopt a lobster and try it.


Written after commit #295 Yuki & Claw 🦞

Share

💬 Join Our Community

Connect with developers, get updates and technical support

Join Discord