●Information × AI — a vibe-coding explainer
Data
goes out.
Answers
come back.
You type a few words. They leave your phone, cross towers and fibre, reach an AI, and return as an answer. This page shows the whole round trip — every hop, in order, with nothing skipped.
the packet watches you. Leave, and it
returns to neutral.
Tap the stage for a fine ripple. Same face, same size, same light in every state — that consistency is what keeps the animation from jumping. Skill: mascot-lock.
02 /Showcase — the live demo
Watch it
travel.
Press play. One orange packet leaves the phone, becomes a blue answer at the AI, and comes home. Every stage lights up as the packet reaches it. The log below narrates the trip in plain English.
Your phone
Where the message starts — and where the answer lands.
Start / FinishSignal tower
Radio waves carry the packets to the nearest tower.
Hop 1 · WirelessNetwork
Routers and fibre pass the packets hand to hand.
Hops 2–6 · FibreThe AI
Reads the message, thinks in tokens, writes a reply.
The turn thinkingTHE ANSWER APPEARS HERE WHEN THE PACKET RETURNS.
Trip log — plain English
SIMULATED REPLY — the “AI” here is a small on-page script that summarises your own words. No message is sent anywhere, and nothing is stored. Try: “Why is the sky blue?” or “Explain tokens.”
03 /3D — the turntable
The core,
in 3D.
This is the turn — the thinking, in the middle of the trip — as a place you can walk around. Scroll, and the camera orbits the core. Drag, and you spin it yourself. Stop, and the turntable keeps turning on its own, like a showroom display that never quite stops.
The 3D core could not start here.
Your browser blocked WebGL or the 3D library. Everything else on this page still works — press play in the live demo above to watch the same trip travel, packet by packet.
04 /Directory — click a stage to open it
The full
journey.
Ten stages, no shortcuts. Outbound is the message going up; the turn is the thinking; inbound is the answer coming home. Click any stage — hover never opens anything, per the skill.
05 /Skills — in their own folder, grouped
The skills
folder.
Built skills-first. The tutorial’s whole process was written down as one skill, filed in its own folder, then grouped — and this page was built by following those groups, in order. Pick a group, open a file.
Plan before you build
Structure, assets and a style reference come first. Generation comes after. A vague brief is a blind box.
06 /Anatomy — what actually travels
Small
packets.
Big idea.
Your message never travels as one piece. It is chopped into small packets, each labelled with where it belongs, so the network can route around trouble and the AI can put it back together in the right order.
Think of it like posting a letter in pieces — every envelope carries the address, a page number, and a seal. Lose one envelope and only that page is re-sent, never the whole letter.
≈ 62% of the packet
≈ 12% of the packet
≈ 8% of the packet
≈ 18% of the packet
Sizes are illustrative — real packets vary by network and app. The proportions are the point: most of the packet is your words; the rest is what gets them there safely.
07 /Build log — the tutorial’s full process, done
Plan → build →
fix → ship.
The Douyin tutorial’s twelve steps, followed end to end for this theme. One class of fix per pass. Nothing vague — every fix named the exact spot.
Deployment follows the standing rule for public pages: this draft is shown first; it goes to GitHub Pages only on your go-ahead. New chapters or links later go in as data, not as a rebuild — see data-not-markup.md in the skills folder.