How "We Can Make a Game, Right? lol" Led to a Custom Protocol in One Day

It Started with Just a Casual Chat

Programming experience: six weeks.

To be precise, six weeks ago I was someone with absolutely zero programming experience.

Two weeks into using Claude Code, I'd gotten pretty comfortable with the daily routine of developing through conversation with AI. Then a thought just popped into my head.

Yeah, it was just a whim. At that point, anyway.

An RPG with Zero Image Files Actually Worked

The result was a cyberpunk RPG called "NEON CIRCUIT."

It has turn-based battles, leveling up, a shop, NPC dialogue, and even a boss fight.

Zero asset hunting. Zero copyright issues. Everything lives inside the code.

It all started from a morning chat and got this far in a few hours. At that point, I had a feeling this day was going to be something special.

Viewing 18 Projects on a Single Screen

Riding the momentum from the game, we moved on to the next topic.

"While we're at it, let's build a dashboard to see all my projects at a glance."

I'm currently running 18 projects simultaneously (SaaS, blogs, landing pages, bots, automation tools, etc.). Honestly, even I had lost track of what was going on where.

The dashboard I named Command Center is already running in production. The same person who was building a game in the morning had deployed a dashboard by afternoon.

The Moment Gmail Became a "Bridge"

While building the dashboard, I needed to pass data between Claude Web and Claude Code. But the two aren't directly connected.

As I was thinking about what to do, something clicked.

If we route through Gmail, we can communicate bidirectionally.

The web version can create Gmail drafts. The Code version can read and write emails via the Gmail API. That means Gmail becomes a communication channel linking the two Claudes.

I tested it, and it actually worked. Watching two AIs exchange emails was pretty surreal.

Compressing 37,668 Characters Down to 245

The Gmail integration was a success. But a problem emerged.

When I tried pasting a large code file (37,668 characters) into an email body, it exceeded the size limit.

"Then let's compress it"—and that's how ROCK PROTOCOL development began.

After five iterations of improvement, the conclusion was simple.

Not "compress then diff"—but "diff then compress."

That single change in order made the difference between 11,366 characters and 245.

The Full Day's Output

All of it started from "We can make a game, right? lol."

There was no plan. With each thing I built through the natural flow of conversation, the next challenge revealed itself—and solving it gave birth to something new.

AI Is a Tool—But How You Use It Changes Everything

Six weeks ago, I couldn't write a single line of code.

Today, I built a custom compression protocol.

Maybe what you really need isn't programming knowledge—it's the curiosity to think, "What if I could do even more?"